#commonjs — Public Fediverse posts

9 Times the Web Platform Was Influenced by Libraries, by @jadjoubran.io:

https://jadjoubran.io/blog/web-platform-influenced-by-libraries

#webplatform #retrospectives #libraries #dojo #bootstrap #jquery #mootools #prototypejs #esm #commonjs

9 Times the Web Platform Was Influenced by Libraries, by @jadjoubran.io:

https://jadjoubran.io/blog/web-platform-influenced-by-libraries

#webplatform #retrospectives #libraries #dojo #bootstrap #jquery #mootools #prototypejs #esm #commonjs

Node.js Package Configuration Guide, by @nodejs:

https://nodejs.github.io/package-examples/

#guides #packages #dependencies #configuration #commonjs #esm

Node.js Package Configuration Guide, by @nodejs:

https://nodejs.github.io/package-examples/

#guides #packages #dependencies #configuration #commonjs #esm

It's almost 2026 and we are still dealing with #commonjs vs #ESM issues in #nodejs. 2026 will be the last year that Keyv (https://keyv.org ) attempts to support commonjs with v6 due out this year. In 2027 we will move to ESM only with v7. It is just too painful to support commonjs compatibility.

This will also mean that `cache-manager`, `cacheable`, etc... will all move to ESM only in 2027. That is a large amount of caching usage across projects.

#typescript #javascript

It's almost 2026 and we are still dealing with #commonjs vs #ESM issues in #nodejs. 2026 will be the last year that Keyv (https://keyv.org ) attempts to support commonjs with v6 due out this year. In 2027 we will move to ESM only with v7. It is just too painful to support commonjs compatibility.

This will also mean that `cache-manager`, `cacheable`, etc... will all move to ESM only in 2027. That is a large amount of caching usage across projects.

#typescript #javascript

Shipping Node.js Packages in 2025, by @joyeecheung:

https://github.com/joyeecheung/talks/blob/master/nordic_js_2025/shipping-nodejs-packages-in-2025.pdf

#slides #nodejs #esm #commonjs #dependencies

Shipping Node.js Packages in 2025, by @joyeecheung:

https://github.com/joyeecheung/talks/blob/master/nordic_js_2025/shipping-nodejs-packages-in-2025.pdf

#slides #nodejs #esm #commonjs #dependencies

#Development #Announcements
Storybook is going ESM-only · The popular UI builder drops CommonJS support https://ilo.im/16744v

_____
#Storybook #JavaScript #ESM #CommonJS #Frameworks #UiComponents #DesignSystems #WebDev #Frontend

#Development #Announcements
Storybook is going ESM-only · The popular UI builder drops CommonJS support https://ilo.im/16744v

_____
#Storybook #JavaScript #ESM #CommonJS #Frameworks #UiComponents #DesignSystems #WebDev #Frontend

Пока, dual packaging: в каком формате публиковать npm-библиотеки

Уже 10 лет в JS-экосистеме воюют два формата модулей: CommonJS и ES Modules. Чтобы и получить плюшки ESM, и не распугать пользователей, npm-пакеты часто используют dual packaging: собирают код в оба формата. Это решает одну проблему, но создает несколько новых. Сегодня расскажу Какие проблемы пришли к dual packaging, и не пора ли от него отказаться. В какой формат паковать npm-библиотеки в 2025 году. Статься будет полезна и для опенсорса, и для внутренних библиотек, и для простых разработчиков (хотя бы чтобы понимать, откуда у вас в node_modules 2 Гб).

https://habr.com/ru/articles/933754/

#npm #esm #nodejs #commonjs #javascript #opensourse

Bridging CommonJS and ESM in Node.js, by @joyeecheung (@webhackfest):

https://www.youtube.com/watch?v=YRueCer2kig

#videos #nodejs #commonjs #esm

Bridging CommonJS and ESM in Node.js, by @joyeecheung (@webhackfest):

https://www.youtube.com/watch?v=YRueCer2kig

#videos #nodejs #commonjs #esm

Building the Bridge: Running JavaScript Modules From Dart, by (not found on Mastodon or Bluesky):

https://globe.dev/blog/building-the-bridge/

#javascript #modules #esm #commonjs #dart #deno

Building the Bridge: Running JavaScript Modules From Dart, by (not found on Mastodon or Bluesky):

https://globe.dev/blog/building-the-bridge/

#javascript #modules #esm #commonjs #dart #deno

[Перевод] Публикация пакета npm с ESM и TypeScript

За последние 2 года поддержка ESM в TypeScript, Node.js и браузерах сильно улучшилась. В этой статье я объясню мою современную настройку, которая является относительно простой по сравнению с тем, что нам приходилось делать раньше: она предназначена для пакетов, которые могут пренебречь обратной совместимостью. Настройка хорошо работает для меня некоторое время — начиная с TS 4.7 (24.05.2022) помогает то, что Node.js теперь поддерживает require(esm) — запрос библиотек ESM из модулей CommonJS я использую только tsc , но упоминаю поддержку других инструментов в разделе "Компиляция TS с помощью других инструментов" Обратная связь приветствуется: что вы делаете по-другому? Что может быть улучшено? Пример пакета: в @rauschma/helpers используется настройка, описываемая в этой статье.

https://habr.com/ru/companies/timeweb/articles/884516/

#timeweb_статьи_перевод #javascript #typescript #ts #npm_package #npm_registry #npm #esm #commonjs #реестр_npm #пакет_npm

#Javascript seems like such a fucking mess when the way you're importing libraries can somehow vary for wtv reason??? I also can never quite comprehend wth's an #ESM or #CommonJS ​:frierencrying:​

#Javascript seems like such a fucking mess when the way you're importing libraries can somehow vary for wtv reason??? I also can never quite comprehend wth's an #ESM or #CommonJS ​:frierencrying:​

@tolmasky the amount of times I had to learn what is #CommonJS and what is #ESM to then forget it and get bitten again when I come to #JS is bleak in comparison, I'm sure, but it made me make a video (mostly for myself) to later watch: https://www.youtube.com/watch?v=SIows5N4BAY

😆

@tolmasky the amount of times I had to learn what is #CommonJS and what is #ESM to then forget it and get bitten again when I come to #JS is bleak in comparison, I'm sure, but it made me make a video (mostly for myself) to later watch: https://www.youtube.com/watch?v=SIows5N4BAY

😆

Want to know why #CommonJS was a mistake?
One phrase. Conditional #module #exports.

if (condition) {
module.exports = foo
} else {
module.exports = bar
}

#javaScript #nodejs #cjs #js #webDev #esm #modules

Want to know why #CommonJS was a mistake?
One phrase. Conditional #module #exports.

if (condition) {
module.exports = foo
} else {
module.exports = bar
}

#javaScript #nodejs #cjs #js #webDev #esm #modules

It's 2024; #JavaScript #libraries should be shipping #ESModules *only*

#webDev #frontend #js #modules #esm #commonjs #modularity #nodejs #deno

It's 2024; #JavaScript #libraries should be shipping #ESModules *only*

#webDev #frontend #js #modules #esm #commonjs #modularity #nodejs #deno

Управление зависимостями в Javascript заходит на новый виток? Работа с ES модулями без сборщиков

Изначально эта статья задумывалась, как рассказ о различиях и назначении полей dependencies , devDependencies и peerDependencies в package.json . Эту тему выбрали ребята в моем телеграм-канале , кстати подписывайтесь, если еще не. Однако, когда я посмотрел количество контента на эту тему, то понял, что его достаточно даже в русском сегменте. При этом я прочитал одну статью , которая показалась мне очень хорошей, а также там были мысли на тему будущего управления зависимостями. В итоге, я решил кратко пересказать вышеупомянутую статью, чтобы лучше самому усвоить тему, а также набросать проект по управлению зависимостями прямо на клиенте, через ES Modules. Так что вы можете прочитать либо оригинальную и полную статью у автора, либо сокращенную версию в первой половине этой статьи. А разбор работы ESM будет во второй половине .

https://habr.com/ru/articles/825424/

#npm #yarn #pnpm #javascript #node #esm #commonjs #dependency_management #package_manager

Is it wrong if I'm kind of enjoying the drama about #ljharb?
Burn tc39 down! Make the web anew!
The only standard is death comes to everything!

#webDev #javaScript #tc39 #nodejs #esm #esmodules #commonjs #cjs #modules

Is it wrong if I'm kind of enjoying the drama about #ljharb?
Burn tc39 down! Make the web anew!
The only standard is death comes to everything!

#webDev #javaScript #tc39 #nodejs #esm #esmodules #commonjs #cjs #modules

> enough libraries use ES Modules that for many projects you need to either use ES Modules, or figure out how to interoperate ES Modules with your CommonJS code. At the same time, enough code still uses CommonJS that you often need to figure out how to include that legacy code in your otherwise-ES Module project.

https://borischerny.com/javascript,/typescript/2024/06/19/ES-Modules-Are-A-Mess.html

#javaScript #nodeJS #esModules #webdev #web #typescript #esm #cjs #commonjs #package #npm

> enough libraries use ES Modules that for many projects you need to either use ES Modules, or figure out how to interoperate ES Modules with your CommonJS code. At the same time, enough code still uses CommonJS that you often need to figure out how to include that legacy code in your otherwise-ES Module project.

https://borischerny.com/javascript,/typescript/2024/06/19/ES-Modules-Are-A-Mess.html

#javaScript #nodeJS #esModules #webdev #web #typescript #esm #cjs #commonjs #package #npm

> Support for require()ing ESM graphs is now exposed by default in Node.js 22

https://openjsf.org/blog/nodejs-22-available

#nodejs #webDev #javaScript #esm #esmodules #commonJS #js #web #node

> Support for require()ing ESM graphs is now exposed by default in Node.js 22

https://openjsf.org/blog/nodejs-22-available

#nodejs #webDev #javaScript #esm #esmodules #commonJS #js #web #node

The only thing I miss from #CommonJS imports is ability to have optional dependencies.

```js
let dep = null;
try {
dep = require('opt-dep')
} catch {}
```

The closest thing in #ESM you can get is import via top-level await, but it's not always available and causes all sorts of funky things.

Learn to create libraries compatible with both ESM and CommonJS, as well as different runtimes like Node.js, Deno, and browsers.

#deno #bun #node #esm #commonjs #javascript

https://hexagon.56k.guru/posts/dual-mode-cross-runtime-packages/

Learn to create libraries compatible with both ESM and CommonJS, as well as different runtimes like Node.js, Deno, and browsers.

#deno #bun #node #esm #commonjs #javascript

https://hexagon.56k.guru/posts/dual-mode-cross-runtime-packages/

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/

#JavaScript #TypeScript #ESM #CommonJS

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/

#JavaScript #TypeScript #ESM #CommonJS

https://gist.github.com/lil5/f2163f18ba67ae51a7f67a329294ca4b

I finally managed to get #NodeJS working with #Typescript without using #CommonJS

This was the only resource that actually worked: https://www.youtube.com/watch?v=H91aqUHn8sE&pp=ygUabm9kZW5leHQgbW9kdWxlIHJlc29sdXRpb24%3D

As supporting both #CommonJS and #ESModules can be wrongly done in a thousand ways, I published why and how we achieved that on fast-check. #JavaScript #opensource

This article is a follow-up of issues reported via #publint from @bluwy and fixed thank to @AndaristRake. As making the package right was not an easy game at first glance, I thought that a how-we-do article could help other #maintainers.

Link to the article: https://fast-check.dev/blog/2023/09/04/dual-packages-or-supporting-both-cjs-and-esm/

As supporting both #CommonJS and #ESModules can be wrongly done in a thousand ways, I published why and how we achieved that on fast-check. #JavaScript #opensource

This article is a follow-up of issues reported via #publint from @bluwy and fixed thank to @AndaristRake. As making the package right was not an easy game at first glance, I thought that a how-we-do article could help other #maintainers.

Link to the article: https://fast-check.dev/blog/2023/09/04/dual-packages-or-supporting-both-cjs-and-esm/

@GabeMoralesVR I am a complete newbie of Javascript. Modules have created a lot of difficulties as I do not yet understand how they work and the documentation is confusing as some Emscripten exemples refer to #CommonJS whereas browsers prefer #ES6.

@GabeMoralesVR I am a complete newbie of Javascript. Modules have created a lot of difficulties as I do not yet understand how they work and the documentation is confusing as some Emscripten exemples refer to #CommonJS whereas browsers prefer #ES6.

In 2009, #CommonJS was exactly what #JavaScript needed. The group took a tough problem and forced through a solution that continues to be used millions of times a day.

But with #ESM as the standard and the focus shifting towards cloud primitives — the edge, browsers, and #serverless compute — and CommonJS simply doesn’t cut it. ESM is a better solution for developers, as they can write browser-compliant code — and for users who get a better end experience.

https://deno.com/blog/commonjs-is-hurting-javascript

#webDev

In 2009, #CommonJS was exactly what #JavaScript needed. The group took a tough problem and forced through a solution that continues to be used millions of times a day.

But with #ESM as the standard and the focus shifting towards cloud primitives — the edge, browsers, and #serverless compute — and CommonJS simply doesn’t cut it. ESM is a better solution for developers, as they can write browser-compliant code — and for users who get a better end experience.

https://deno.com/blog/commonjs-is-hurting-javascript

#webDev

Should I transpile this code? I really want to use Typescript and new JS features?

Do I want to support #ESModules and #CommonJS? Should I bundle this code? What about #Node vs. #Deno Browser vs. compatibility?

Should I transpile this code? I really want to use Typescript and new JS features?

Do I want to support #ESModules and #CommonJS? Should I bundle this code? What about #Node vs. #Deno Browser vs. compatibility?

npm packages: Share of ESM vs. CommonJS?
https://github.com/wooorm/npm-esm-vs-cjs
#ES_Next_News #ECMAScript #JavaScript #ESM #CommonJS #npm

npm packages: Share of ESM vs. CommonJS?
https://github.com/wooorm/npm-esm-vs-cjs
#ES_Next_News #ECMAScript #JavaScript #ESM #CommonJS #npm

I am creating a library using #typescript I would like to generate using the same codebase a valid #deno import, an #javascript #ESM module and #CommonJS module for maximum compatibility. Does anyone have a magic tsconfig configuration in the best case, or any idea about an easy solution to achieve this?

I am creating a library using #typescript I would like to generate using the same codebase a valid #deno import, an #javascript #ESM module and #CommonJS module for maximum compatibility. Does anyone have a magic tsconfig configuration in the best case, or any idea about an easy solution to achieve this?

2/ If a CommonJS module follows this rule, its exports can be name-imported from ESM modules: https://2ality.com/2022/10/commonjs-named-exports.html
#JavaScript #CommonJS #ESM #NodeJS

1/ Happy to see that ESM modules have become popular in current code bases (*):
– Mostly ESM: 68%
– Mostly CommonJS: 17%
– A mix: 12%
– (No answer: 3%)

In my own (relatively simple) ESM-based Node.js projects I was delighted that I usually couldn’t even tell if a dependency was ESM or CommonJS.

(*) https://fosstodon.org/@rauschma/109824102084164590
#JavaScript #CommonJS #ESM #NodeJS

Anyone know something about ESM, CommonJS, Typescript and how they interact?

Stuck on a problem, posted on Stack overflow:

https://stackoverflow.com/questions/75354770/isomorphic-dirname-in-esm-and-commonjs

#node #typescript #esm #commonjs