import-map-deployer
es-module-shims
import-map-deployer | es-module-shims | |
---|---|---|
3 | 13 | |
184 | 1,488 | |
2.7% | - | |
4.6 | 6.5 | |
6 months ago | 16 days ago | |
JavaScript | JavaScript | |
Apache License 2.0 | 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.
import-map-deployer
-
⏰ It’s time to talk about Import Map, Micro Frontend, and Nx Monorepo
You should have a look to them import-map-deployerlibrary which enable to update animportmap.json directly on the server
-
You Might Not Need Module Federation: Orchestrate your Microfrontends at Runtime with Import Maps
The lightweight Nest.js Import Map Resolver server has two main roles: store and update the importmap, but also handle the submission of JS assets. Single-spa has a similar solution available.
-
Micro Frontends: After one year with Single-SPA
As a single deployment pipeline and repository is used for all the apps, we are not gaining from one of the main benefits of using micro frontends architecture which is independent release cycles for each app. But by putting everything in a single repository we could achieve what we were looking for without dealing with the complexity of managing multiple repositories and deciding on how to update import maps (solutions like import-map-deployer).
es-module-shims
-
⏰ It’s time to talk about Import Map, Micro Frontend, and Nx Monorepo
For full compatibility and extra features, we usually use the library es-module-shims.
-
JavaScript import maps are now supported cross-browser
You can polyfill for unsupported browsers, it works surprisingly well: https://github.com/guybedford/es-module-shims
-
Modern SPAs without bundlers, CDNs, or Node.js
https://github.com/guybedford/es-module-shims has a polyfill. (But it is fairly large: 53KB raw, 15KB gzipped, 32KB minified, 11KB minified+gzipped. It’s providing a lot of likely-unnecessary functionality. I’d prefer a stripped-down polyfill that can also be lazily-loaded, controlled by a snippet of at most a few hundred bytes that you can drop into the document, only loading the polyfill in the uncommon case that it’s needed—like how five years ago as part of modernising some of the code of Fastmail’s webmail, I had it fetch and execute core-js before loading the rest iff !Object.values (choosing that as a convenient baseline), so that the cost to new browsers of supporting old browsers was a single trivial branch, and maybe fifty bytes in added payload.)
- Writing JavaScript without a build system
-
Modern SPAs without bundlers, CDNs, or NodeJS
If we call the shim a framework, would you be ok with it then?
-
Import maps 101
If you want import maps to be supported in any browser, there is an ES Module Shims polyfill which is compatible with any browser that has baseline ES Module Support (i.e. Edge 17+, Firefox 60+, Safari 10.1+, and Chrome 61+).
-
Everything You Need to Know About JavaScript Import Maps
An example of a polyfill that can be used is the ES Module Shims polyfill that adds support for import maps and other new module features to any browser with baseline support for ES modules (about 94% of browsers). All you need to do is include the es-module-shim script in your HTML file before your import map script:
-
How bad is it to not use a bundler?
i often use es-module-shims so i can load npm packages in browsers without a bundler 😎
-
Fresh – The next-gen web framework
I explored using client-side service workers for build-less deployment workflows a while back, but the blocker was the initial visit when the service worker hasn't been installed yet. Ended up using es-module-shim's fetch hook (https://github.com/guybedford/es-module-shims#fetch-hook) instead, which worked quite well.
I kept the demo repo around here, in case it's helpful to anyone: https://github.com/lewisl9029/buildless-hot-reload-demo.
The repo itself is quite out of date at this point, but my current project, Reflame, is essentially the spiritual successor: https://reflame.app/
Reflame has the same ideals of achieving the developer experience I've always wanted for building client rendered React apps:
- instant production deployments (usually <200ms)
- instant preview environments that match production in pretty much every imaginable way (including the URL), that can also be flipped into development mode for fast-refresh (for the seamless feedback loop we're used to in local dev) and dev-mode dependencies (for better error messaging, etc)
- close-to-instant browser tests (1-3 seconds) that enable image snapshot comparisons that run with maximum parallelism and only rerun when their dependency graphs change
-
Do you use Import-Map for your client-side ESM?
The problem of course is that browser-support for Import Maps is sadly lacking (only Chrome/Chromium-based at time of writing). There are tricks/shims to get around this, like ES-Module-Shims. I find these approaches to be a little too intrusive, personally.
What are some alternatives?
navbar - The navbar microfrontend
import-maps - How to control the behavior of JavaScript imports
hyperscript - Create HyperText with JavaScript.
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript 🚀
Rust Language Server - Repository for the Rust Language Server (aka RLS)
import-map-overrides - A browser and NodeJS javascript library for overriding import maps
stampino-element
module-federation-plugin
import-remap - Rewrite ES module import specifiers using an import-map.
esm.sh - A fast, smart, & global CDN for modern(es2015+) web development.
mercury - A truly modular frontend framework