es-module-shims
Alpine.js
Our great sponsors
es-module-shims | Alpine.js | |
---|---|---|
13 | 242 | |
1,481 | 26,798 | |
- | 1.8% | |
6.5 | 9.3 | |
9 days ago | 5 days ago | |
JavaScript | HTML | |
MIT License | 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.
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.
Alpine.js
-
Biometric authentication with Passkeys
Alpine.js for reactive frontend
-
🤓 My top 3 Go packages that I wish I'd known about earlier
✨ In recent months, I have been developing web projects using GOTTHA stack: Go + Templ + Tailwind CSS + htmx + Alpine.js. As soon as I'm ready to talk about all the subtleties and pitfalls, I'll post it on my social networks.
-
Htmx Is Composable?
> But honestly, torn towards htmx but undecided.
We are in the middle of migrating from our monster react application into server rendered pages (with jinja2). The velocity at which we are able to ship and the reduction of complexity has been great so far.
Managing client side state for simple things like (is the dropdown open/closed), listening to keyboard events and such can be done with something like alpine-js [1] without all the baggage that something like react brings.
It appears this is already the trend with JS frameworks too - with server side rendering being the new norm.
[1] https://alpinejs.dev/
- Pocketbase: Open-source back end in 1 file
-
Coming to grips with JS: a Rubyist's deep dive
Sure, you can use any number of JS-avoidance libraries. I'm a fan of Turbo, and there's also htmx, Unpoly, Alpine, hyperscript, swup, barba.js, and probably others.
-
What is your opinion about developers who do direct DOM manipulations instead of using modern web frameworks (like React, Vue, Angular) to achieve maximum performance?
Direct DOM, but with a library. Specifically AlpineJS since it follows Vue closely in design practices allowing me to scale into a full web application if necessary (basically swapping to Vue takes minimal work). The Morph plugin is specifically what I like using.
-
Kicking the tires with NestJS and Hotwire: Part II
If you want more details on the initial setup I encourage you to take a look at the Part I that covers more of the initial implementation. For this portion, I added Prisma as an ORM, a frontend style library called Tachyons, and AlpineJS to handle any client-side interactions. I did this to avoid needing to add a client-side bundler to the build and instead just rely on plain old module imports to compose the frontend. This is now the default for Rails and it is quite nice to not need any additional build tools for the client.
-
Deveplop a simple GUI app by Wails use Golang
- [swallow-pywebview](https://github.com/rangwea/swallow-pywebview): Base on [pywebview](https://pywebview.flowrl.com/) using Python,the frontend base on [alpinejs](https://alpinejs.dev/) and [tailwindcss](https://tailwindcss.com/)。
-
How to Make an Animated Number Counter with Tailwind CSS
If you’ve followed our other tutorials, you might be familiar with Alpine.js. It’s a lightweight JavaScript library that allows you to add interactivity to your site without writing a single line of JavaScript. It’s incredibly easy to use, and we’ll show you how to make the animation trigger when the user scrolls to it.
-
A First Look at HTMX and How it Compares to React
The approach is not new, essentially a variation of Knockout, Alpine, and similar "JS-in-HTML" approaches.
What are some alternatives?
import-maps - How to control the behavior of JavaScript imports
Svelte - Cybernetically enhanced web apps
hyperscript - Create HyperText with JavaScript.
petite-vue - 6kb subset of Vue optimized for progressive enhancement
Rust Language Server - Repository for the Rust Language Server (aka RLS)
htmx - </> htmx - high power tools for HTML
stampino-element
React - The library for web and native user interfaces.
import-remap - Rewrite ES module import specifiers using an import-map.
Stimulus - A modest JavaScript framework for the HTML you already have [Moved to: https://github.com/hotwired/stimulus]
mercury - A truly modular frontend framework