aleph.js
es-module-shims
aleph.js | es-module-shims | |
---|---|---|
13 | 13 | |
5,249 | 1,486 | |
0.0% | - | |
6.6 | 6.5 | |
9 months ago | 5 days ago | |
TypeScript | JavaScript | |
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.
aleph.js
-
I don't get fresh. why can't I use react without commiting to a server side framework?
Check aleph if you want to use react with deno. But I'd suggest sticking with Node.js and Vite as you'll get less surprises.
-
Modern SPAs without bundlers, CDNs, or Node.js
Here's another thing: if you want to grow from this exact setup, use deno. It has support for import maps and don't require a bundler or a separate compilation step for typescript
https://deno.land/[email protected]/basics/import_maps
Maybe add aleph too (which is similar to nextjs)
https://alephjs.org/
Deno won't require nearly as much tooling as nodejs, but it still has tooling for the cases you need it.
- Deno 1.28: Featuring 1.3M New Modules
-
Fresh is a new full stack web framework for Deno
There’s also https://alephjs.org, never used but pops up when you search for "deno react" so I assume is similar to nextjs.
- Aleph.js – Fullstack Framework in Deno
-
Using Ultra, the new React web framework
Aleph.js is a full-stack framework in Deno, used as an alternative to Next.js. Aleph.js offers features like ES module imports, file-system routing, SSR & SSG, and HMR with a fast refresh.
- Aleph.js is a fullstack framework in Deno, inspired by Next.js
- The Fullstack Framework in Deno
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?
ultra - Zero-Legacy Deno/React Suspense SSR Framework
import-maps - How to control the behavior of JavaScript imports
fresh - The next-gen web framework.
hyperscript - Create HyperText with JavaScript.
vitext - The Next.js like React framework for better User & Developer experience!
Rust Language Server - Repository for the Rust Language Server (aka RLS)
inertia-laravel - The Laravel adapter for Inertia.js.
stampino-element
marky - A modular and extensible ESM and Deno Markdown parser.
import-remap - Rewrite ES module import specifiers using an import-map.
derby - MVC framework making it easy to write realtime, collaborative applications that run in both Node.js and browsers
mercury - A truly modular frontend framework