JSPM

JSPM 4.0 Release jspm.org/jspm-4.0-relea…

@ghoullier Thanks for confirming. Definitely looks like the old styles. I just tried turned off the cloudflare cache, does that help?

@jspm I just tested it in incognito more and same issue.

JSPM 4.0 Release jspm.org/jspm-4.0-relea…

@ghoullier Thanks for the info. The underlines on the sidebar are from the old stylesheet. This should be cache busted though - can you confirm it's definitely not the cache?

@jspm Thanks for the release. FYI the website is not very accessible in dark mode.

JavaScript integrity manifests with the recently supported import maps integrity field. jspm.org/js-integrity-w…

JSPM is deprecating support for the old JSPM dev dynamic modules CDN. The project is now an import-maps-only CDN & toolchain. jspm.org/jspm-dev-depre…

@borkdude If this is still happening, please copy the hex data in cachefly.cachefly.net/CacheFlyDebug and post this as a new issue on github.com/jspm/project/i…, and we'll look into it further.

@jspm Why am I getting a 404 for this url? @0.4.44/core.js" target="_blank" rel="nofollow noopener">ga.jspm.io/npm:squint-clj…

@wasjustfrontin @angel_d_munoz @evanplaice JSPM CLI defaults to a central "importmap.json" workflow, where `jspm link a.html -o a.html` then plucks individual mappings for an HTML file while retaining the version locks from the main importmap.json file.

The Vanilla stack: Module: ESM Package manager: NPM Bundler: ESBuild Compiler: None Components: Web Components Types: JSDoc Test: No standout best option yet

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. jspm.org/jspm-cli

If you love the idea of importmaps, now is @jspm's time to shine! jspm.org

JavaScript import-maps are now supported cross-browser! 🗺️ web.dev/import-maps-in… <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. github.com/guybedford/es-…

I wrote a little bit about the process and the utilities by @jspm to make this happen. Bringing deno style importmap resolutions to node. jkrishna.dev/post/import-ma…

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 - twitter.com/jspm/status/16….

Import Maps even have production benefits for applications that utilize far-future expires caching strategies, by allowing fine-grained caching of modules. See #mapping-away-hashes-in-script-filenames" target="_blank" rel="nofollow noopener">github.com/WICG/import-ma… for more info on this topic.

🟨 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.