JSPM 4.0 Release https://t.co/JYDRWR0lUG

JavaScript integrity manifests with the recently supported import maps integrity field. https://t.co/6sZr9Pkfry

JSPM is deprecating support for the old JSPM dev dynamic modules CDN. The project is now an import-maps-only CDN & toolchain. https://t.co/lUiV0dKgdV

Native JS import maps + package.json + automatic CLI code generation @jspm is the beginning next-generation of developer tooling – try it out!

Announcing the relaunch of the JSPM CLI for import map package management.

Announcing the relaunch of the JSPM CLI for import map package management.

If you love the idea of importmaps, now is @jspm's time to shine! https://t.co/5nQbNdZkIj

JavaScript import-maps are now supported cross-browser! 🗺️ https://t.co/el56VvP1XZ <script type="importmap"> can define a mapping of external module names to their corresponding URLs, making it easier to use in your code.

With the release of Safari 16.4 today, import maps are now supported across all major browsers! (to be followed closely by modulepreload support) es-module-shims 1.7.1 was just released, fully polyfilling import maps for only the remaining 26% of users. https://t.co/tnlzPxXGHG

With the release of Safari 16.4 today, import maps are now supported across all major browsers! (to be followed closely by modulepreload support) es-module-shims 1.7.1 was just released, fully polyfilling import maps for only the remaining 26% of users. https://t.co/tnlzPxXGHG

I wrote a little bit about the process and the utilities by @jspm to make this happen. Bringing deno style importmap resolutions to node. https://t.co/D4REB2uwv2

Wow, I'm really in love with @jspm . I'm glad to see a package manager specifically designed for a buildless development workflow. Cross browser import maps support can't come quickly enough

Working on the @jspm CLI as an import map package manager👀

Thanks for reading and follow for regular updates on modern modules workflows. If you missed our previous post on an introduction to module scripts, you can find that here - https://t.co/sgxDSezY5x.

Import Maps even have production benefits for applications that utilize far-future expires caching strategies, by allowing fine-grained caching of modules. See https://t.co/NancHx713A for more info on this topic.

While Import Maps aren’t yet fully supported in all browsers, there’s a production-suitable polyfill, ES Module Shims ( https://t.co/tnlzPxX8S8). ES Module Shims polyfills Import Maps for all browsers with ES modules support. It just requires including via a script tag.

Lit still gives an error, as it needs its dependency mappings in order to work. These dependencies can also be defined in the import map to get the complete resolution and correct execution.

Here’s how to define Import Maps in HTML files. In the example, Lit is imported as a bare specifier, which the import map will then map to its URL in the local node_modules folder. Import Maps can map any module specifiers via these mappings in a type=”importmap” script tag.

🟨 Did you know that the browser has its own custom module resolver? Import Maps are a new feature for customizing module resolution. Supported in Chrome, they landed in Safari TP and flagged in Firefox this year. Consider this example, which throws as it can’t find Lit.

This was the second post of the JSPM module workflow introduction series, we'll be covering further native modules workflow topics in future posts. See below for our previous introduction to https://t.co/aDzVC95bbs.