hello-esm-firebase
esm
| hello-esm-firebase | esm | |
|---|---|---|
| 1 | 2 | |
| 0 | 5,252 | |
| - | - | |
| 1.3 | 0.0 | |
| over 2 years ago | 8 months ago | |
| JavaScript | JavaScript | |
| - | GNU General Public License v3.0 or later |
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.
hello-esm-firebase
-
Node 16 support is on!
Hello World Example
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:
What are some alternatives?
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.
semantic-release - :package::rocket: Fully automated version management and package publishing
graphql-upload - Middleware and an Upload scalar to add support for GraphQL multipart requests (file uploads via queries and mutations) to various Node.js GraphQL servers.
react-firebase-starter - Boilerplate (seed) project for creating web apps with React.js, GraphQL.js and Relay
oletus - Minimal ECMAScript Module test runner
react-static-boilerplate - Boilerplate (seed) project for creating web apps with React.js, GraphQL.js and Relay [Moved to: https://github.com/kriasoft/react-firebase-starter]
nanoexpress - Professional backend framework for Node.js
node - Node.js JavaScript runtime ✨🐢🚀✨
webpack-common-shake - CommonJS Tree Shaker plugin for WebPack
alameda - AMD loader, like requirejs, but with promises and for modern browsers
base64-transcode - Base64 encoding and decoding for both browser and node, with binary file support.