esm
jsdelivr
Our great sponsors
esm | jsdelivr | |
---|---|---|
2 | 3 | |
5,252 | 5,374 | |
- | 1.4% | |
0.0 | 5.7 | |
8 months ago | 2 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:
jsdelivr
-
Cloudflare is slow and Cloudflare cant do much about it
Russia has blocked Cloudflare too too. You can see it in the issues for jsDelivr (which apparently handles a lot of traffic for TASS, since they use the CDN and browsers don't share caches for privacy reasons). https://github.com/jsdelivr/jsdelivr/issues/762
- The certificate of jsdelivr is hijacked in China and is inaccessible
-
appfleet, a new edge compute platform goes live
And if you are a non-profit or an open source project let us know to get sponsored with free services. We even offer free design services
What are some alternatives?
hello-esm-firebase - 🔥 ESM in Cloud Functions (via Firebase)
esm.sh - A fast, smart, & global CDN for modern(es2015+) web development.
semantic-release - :package::rocket: Fully automated version management and package publishing
npm-expansions - Send us a pull request by editing expansions.txt
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.
action - 📦📊 GitHub Action to reports on the size of your npm package
oletus - Minimal ECMAScript Module test runner
cf-b2cdn - Serve private/public B2 bucket files and optionally list directories using Cloudflare's CDN
nanoexpress - Professional backend framework for Node.js
nodebestpractices - :white_check_mark: The Node.js best practices list (February 2024)
node - Node.js JavaScript runtime ✨🐢🚀✨
yarn - The 1.x line is frozen - features and bugfixes now happen on https://github.com/yarnpkg/berry