https://github.com/nodejs/node/issues/58663
https://github.com/nodejs/node/issues/58663
Built-in support for:
◆ @rollup/plugin-node-resolve
◆ @rollup/plugin-json
◆ @rollup/plugin-commonjs
More below...
Built-in support for:
◆ @rollup/plugin-node-resolve
◆ @rollup/plugin-json
◆ @rollup/plugin-commonjs
More below...
While I did want to keep support for as long as possible, dependencies dropping support for CommonJS make it harder and harder to do. So it is time to join.
Soon I'll release new major versions of all packages, without CommonJS
While I did want to keep support for as long as possible, dependencies dropping support for CommonJS make it harder and harder to do. So it is time to join.
Soon I'll release new major versions of all packages, without CommonJS
github.com/joyeecheung/...
github.com/joyeecheung/...
www.11ty.dev/docs/cjs-esm/
Which should you choose? It depends! The social-media sized answer is: ESM 😅
www.11ty.dev/docs/cjs-esm/
Which should you choose? It depends! The social-media sized answer is: ESM 😅
TEN YEARS
after JavaScript modules have been standardized.
TEN YEARS
after JavaScript modules have been standardized.
imagine how much data will be saved once people stop shipping dual-packages. prettier is one of many
imagine how much data will be saved once people stop shipping dual-packages. prettier is one of many
Lessons learned moving Eleventy (@11ty.dev) from CommonJS to ESM.
www.zachleat.com/web/eleventy...
New talk video and slides from CFE’s TheJamDev event.
Lessons learned moving Eleventy (@11ty.dev) from CommonJS to ESM.
www.zachleat.com/web/eleventy...
New talk video and slides from CFE’s TheJamDev event.
Slides at github.com/joyeecheung/...
Slides at github.com/joyeecheung/...
- @joyeecheung.bsky.social revealed how @nodejs.org is moving to full ESM and why the future looks brighter for developers.
www.youtube.com/watch?v=I0jv...
- @joyeecheung.bsky.social revealed how @nodejs.org is moving to full ESM and why the future looks brighter for developers.
www.youtube.com/watch?v=I0jv...
- Zero dependencies and MIT licensed
- Supports ESM, CommonJS, and script tag imports
- Define commands with simple keyword matching and wildcard parameters
- Zero dependencies and MIT licensed
- Supports ESM, CommonJS, and script tag imports
- Define commands with simple keyword matching and wildcard parameters
🔶 Type Annotations
🔶 Deprecating CommonJS
🔶 AsyncContext
🔶 Module Declarations
🔶 Type Annotations
🔶 Deprecating CommonJS
🔶 AsyncContext
🔶 Module Declarations
When Node 18 hits EOL in less than 3 months, we can finally drop CJS builds and go ESM-only
When Node 18 hits EOL in less than 3 months, we can finally drop CJS builds and go ESM-only
I know it's simple but I've known programming basics for a long time but never knew how to do that so it feels really cool to build out an organized script library
like a sick fuck
you want to be butter smooth with existing ecosystem *and* as a bonus, can unlock more with emerging tech
wanting atproto to win is great
wanting deno to win is cool too
making atproto projects annoying to run outside deno — huge mistake imo
you want to be butter smooth with existing ecosystem *and* as a bonus, can unlock more with emerging tech
Maybe it's because most backend deps are still stuck with commonjs.
Maybe it's because most backend deps are still stuck with commonjs.