Our great sponsors
-
If you use native ESM code in the browser, do you use Import-Maps to be able to use friendly non-path import-specifiers (like import from "my-app" instead of import from "/path/to/js/my-app.mjs")? I love this feature!
-
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.
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
I personally wrote a build-time tool called Import-Remap that I like to use. At build-time, you can apply an import-map (JSON) to rewrite all the import specifiers in a tree of your files... thereby creating a deployed tree of browser-side JS. This lets me author with nice import specifiers but not worry about lack of browser support. It does unfortunately require a build-step. :(