esm
oletus
Our great sponsors
| esm | oletus | |
|---|---|---|
| 2 | 2 | |
| 5,252 | 45 | |
| - | - | |
| 0.0 | 2.6 | |
| 8 months ago | 5 months ago | |
| JavaScript | JavaScript | |
| GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
esm
-
CommonJS Is Hurting JavaScript
> I think the biggest miss was not making mixed mode (default) for Node do it the way webpack/babel, etc did it by default in terms of interop. I get they wanted to make it more implicit to call cjs from esm, in the end it just inhibits conversion of existing libraries as dependencies are now a bigger hurdle.
Huge huge agreement.
I forget the specifics but there was some super tiny corner case around maybe default exports that could potentially create ambiguity & that spawned a multi-year bellyaching around doing anything at all for interop. What Node got was incredibly hard fought for against much resistance to interop.
But the final compromises made everything so much more painful for everyone. So many esm projects but oh look a .eslintrc.cjs, how unsurprising & sad.
It's extra maddening because node had a wonderful just works (except that tiny tiny tiny corner case) interop via @standard-things/esm, which seamlessly let the two worlds interop. It'd been around for years before node started shipping support, and it was no ceremony just works bidirectional interoperability, and it took basically no effort or thought from the developers point of view to use. It sucked seeing us walk back from great, mired by frivolous over concern for a obscure corner-case.
https://github.com/standard-things/esm
-
ERR_REQUIRE_ESM
2) Stay on ES5. Wrap ES6 module(s) with esm adapter. Just like the documentation says:
oletus
-
Jest not recommended to be used in Node.js due to instanceOf operator issues
I am currently one of the maintainers of Oletus.
[1] https://bun.sh/docs/cli/test
[2] https://github.com/oven-sh/bun/issues/3158
[3] https://github.com/bearror/oletus
- I will pay you cash to delete your NPM module
What are some alternatives?
hello-esm-firebase - 🔥 ESM in Cloud Functions (via Firebase)
dredd - Language-agnostic HTTP API Testing Tool
semantic-release - :package::rocket: Fully automated version management and package publishing
node-cross-spawn - A cross platform solution to node's spawn and spawnSync
webpack - A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
xv - 🙅♀️ ✌️ fastest test runner
nanoexpress - Professional backend framework for Node.js
cynic - simple async run-anywhere js testing framework
node - Node.js JavaScript runtime ✨🐢🚀✨
mocha - ☕️ simple, flexible, fun javascript test framework for node.js & the browser
webpack-common-shake - CommonJS Tree Shaker plugin for WebPack
ava - Node.js test runner that lets you develop with confidence 🚀