
@jspmi
iAccount based inUnited States
About this account
- Account based in
- United States
- Connected via
- Web
Account-level information from X, not a live location or the device used for a specific post.
JavaScript package manager and ES module CDN
Joined November 2009
- Tweets91
- Following0
- Followers351
- Likes29
JavaScript integrity manifests with the recently supported import maps integrity field.
jspm.org/js-integrity-with-i…
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-deprecatio…
JSPM retweeted
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
JSPM retweeted
Announcing the relaunch of the JSPM CLI for import map package management. jspm.org/jspm-cli
Announcing the relaunch of the JSPM CLI for import map package management. jspm.org/jspm-cli
JSPM retweeted
Lit, now with 100% fewer build tools:
lit.dev/playground/#gist=8b4…
JSPM retweeted
JavaScript import-maps are now supported cross-browser! 🗺️ web.dev/import-maps-in-all-m…
<script type="importmap"> can define a mapping of external module names to their corresponding URLs, making it easier to use in your code.
![<script type="importmap">
{
"imports": {
"lodash": "https://unpkg.com/lodash@4.17.21/lodash.js"
}
}
</script>
<script type="module">
import _ from 'lodash';
console.log(_.map([1, 2, 3], (n) => n * 2));
</script>](https://pbs.twimg.com/media/FsUnUVJacAAnMZI.jpg?name=small&format=webp)
ALT <script type="importmap"> { "imports": { "lodash": "https://unpkg.com/[email protected]/lodash.js" } } </script> <script type="module"> import _ from 'lodash'; console.log(_.map([1, 2, 3], (n) => n * 2)); </script>
JSPM retweeted
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-mod…
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-mod…
JSPM retweeted
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-map…
Importmap brought to you in node by brilliant @askjkrishna
Taste first aha moments with new world of URLs.
github.com/JayaKrishnaNambur…
JSPM retweeted
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
JSPM retweeted
Working on the @jspm CLI as an import map package manager👀
🟨 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.
Import Maps even have production benefits for applications that utilize far-future expires caching strategies, by allowing fine-grained caching of modules. See github.com/WICG/import-maps#… for more info on this topic.
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 - xitter.cf/jspm/status/1600238612….
🟨 A brief intro to "module scripts" in browsers, for the unfamiliar.
When adding type="module" to HTML script tags, this enables native module syntax to import any JavaScript module from an embedded script tag without the need for any additional tooling apart from a server.
For larger applications, this "waterfall" can start to become a performance bottleneck. Production module optimization can resolve this problem. which we'll cover in a future post.
npm packages on jspm.dev have this optimization locally applied.
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 jspm.dev. xitter.cf/jspm/status/1597354262…
🟨FYI: You can load any npm module in modern modules browsers using jspm.dev. It even works in the browser console to import any module instantly.











