I hope that the Trump administration's cancellations of the Orion crew capsule (for which Europe built the Service Module) and the early de-orbiting of the ISS is a strong wake-up call that ESA's space program can no longer rely on promises from NASA.
Grateful for Hélène Huby's foresight to leave Airbus when she was VP of Orion-#ESM to develop European space capsules that don't rely on the US honouring their commitments.
New Kitten release 
• Fix for Markdown pages¹: import { Multiple, Exports } … and import { Foo as Bar } … now properly supported in front matter when importing components.
Enjoy!
¹ https://kitten.small-web.org/reference/#markdown-pages-page-md-files
require(esm) was just enabled by default in the latest Node v20!
Node v18 LTS support ends on April 30th, and as of that date you'll officially be able to use ESM & CommonJS together easily in all supported versions 
#nodejs #esm #javascript
https://github.com/nodejs/node/releases/tag/v20.19.0
#Development #Overviews
The state of WebAssembly 2024/2025 · Improvements inside and outside the browsers https://ilo.im/1629ke
_____
#Programming #WebAssembly #WASM #WASI #ESM #JavaScript #Browser #WebDev #Frontend #Backend
#unpopularOpinion ESModules over HTTP are fine and the web doesn't need a bundler or a package manager registry.
If you’re running a relatively recent version of Node.js – I’m on 22.x for Kitten¹ at the moment– and you use ES Modules (because, of course, you use ES Modules, right, because it’s almost 2025…) and you want to use .js extensions and not have to litter package.json files with "type": "module" all over the place, you can start Node with the following flag and it should Just Work™ ;)
--experimental-default-type
Looking forward to presenting at the #European Conference on #Personality in #Berlin 
First breakfast, then talking about #ML-SEM and how they can detect #measurement #bias in intensive #longitudinal #data.
Slides are already online http://dx.doi.org/10.13140/RG.2.2.19561.30560
The long version as #preprint too http://dx.doi.org/10.31219/osf.io/fm253
#ecp #ecp21berlin
#simulation #study #ESM #EMA #SEM #MLSEM
#joinme
Today @MerijnMestdagh came to Tilburg to give two @TilburgU_TESC workshops about the #ESM app m-Path (one on the Basics and on about Advanced capabilities).
Thanks a lot @MerijnMestdagh ! It was a lot of fun and we all learned a lot (including some cool "hidden" tips & tricks)
(Feels good to close two-year-old feature requests.) :)
https://codeberg.org/kitten/app/issues/25
https://codeberg.org/kitten/app/issues/26
THAT is an interesting approach to #ESM: https://github.com/date-fns/date-fns/blob/95b84c7e4ca73975dbd53b0e51b84fd053de99d7/package.json#L19
I wonder how @koss arrived at this particular solution.
A new post on how to create a React components library, although focusing on the aspects of publishing dual libraries (CJS+ESM) with types: https://blog.coderspirit.xyz/blog/2023/09/15/create-a-react-component-lib/
For those working with intensive longitudinal data, as collected via the experience sampling method (ESM) / ecological momentary assessment (EMA): I will be teaching my 'ESM Data Analysis' course again this year (December 6-8). For further info, see:
https://www.wvbauer.com/doku.php/course_esmda
where you will find a course description and schedule, some notes on the course prerequisites / how to prepare for the course, registration instructions, and some notes / frequently asked questions.
I have a new favorite puzzle: #ESM module import and export configurations in libraries, with TypeScript support, of course.
New preprint together with @LeonieVogelsm and @esther: "Assessing and Accounting for Measurement in Intensive Longitudinal Studies: Current Practices, Considerations, and Avenues for Improvement"
The other things I'm experimenting with @Suns be
Export templates, styles, behaviour, all without any framework, published on a controlled domain name, as an #ESM along with a #CustomElement and registration helper
If one project doesn't use customElement, but needs something from it, but in a framework, it's available. It gives liberty to use & extend. Best of both worlds.
That's what I'm aiming for: optimal re-use and to load only what's needed
The things that makes projects heavy and slow
I struggle to understand sometimes why some JavaScript developers are still so attached to using `default` exports... The disadvantages of them seem to be clearly heavier than the advantages you get by using them especially today with modern tooling. #javascript #typescript #esm
Anyone delved with publishing #ESM modules over https like https://deno.land does [1] with version in the URL along with publishing for NPM?
Probably need different URL for Browser, Deno, and make sure the release/testing checks for platform compatibility.
I can imagine writing a release of a package into a publicly available folder with package name platform, and version. Pretty much like deb/rpm. Heh.
Anyone experimented w/ that?
1: https://deno.land/manual@v1.12.1/linking_to_external_code
Can we predict if atmospheric CO2 grows faster or slower than what is expected from emissions' growth?
Yes, by assimilating observational data into an #ESM, we gain a predictive skill of 5 years for the air–sea CO2 flux, and 2 years for the air–land CO2 flux and atmospheric carbon growth rate.
Find out more on how we predict the global carbon cycle and evaluate modeled atmospheric CO2 in our new study
https://mas.to/@HongmeiLi/109834343353355699
SDK developers, how are you handling ESM + CJS? We're starting to see dependencies switch to ESM only, but because we support #CJS, we're unable to upgrade as #ESM can't be imported by CJS
Is the answer just to drop our transpiling to CJS/UMD and go ESM only? That feels like it should be the answer & would technically be a semver-major change.
Is there a better solution?
