Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add JSPM import maps tools #297

Merged
merged 1 commit into from
Nov 22, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -621,14 +621,18 @@ would give you the appropriately-mapped location of `resource.json` within the `

Several members of the community have been working on polyfills and tooling related to import maps. Here are the ones we know about:

* [jspm](https://www.npmjs.com/package/jspm) is a command-line import map package management tool.
* [jspm-vscode](https://marketplace.visualstudio.com/items?itemName=JSPM.jspm-vscode) is a [VSCode](https://code.visualstudio.com) extension for generating, injecting into HTML, and updating import maps.
* https://generator.jspm.io is an online generator for generating import maps.
* [@jspm/generator](https://www.npmjs.com/package/@jspm/generator) is the low-level core library for working with import map generation.
* [@import-maps/resolve](https://www.npmjs.com/package/@import-maps/resolve) resolves a specifier relative to an import map.
* [@jsenv/importmap-node-module](https://www.npmjs.com/package/@jsenv/importmap-node-module) generates an import map from your `package.json` and `node_modules/` directories.
* [@jsenv/importmap-eslint-resolver](https://www.npmjs.com/package/@jsenv/importmap-eslint-resolver) enables import map resolution in [ESLint](https://eslint.org/)
* [@jsenv/importmap-eslint-resolver](https://www.npmjs.com/package/@jsenv/importmap-eslint-resolver) enables import map resolution in [ESLint](https://eslint.org/).
* [@node-loader/import-maps](https://www.npmjs.com/package/@node-loader/import-maps) is a [Node.js loader](https://nodejs.org/dist/latest/docs/api/esm.html#esm_experimental_loaders) for using import maps in Node.js.
* [@web/dev-server-import-maps](https://www.npmjs.com/package/@web/dev-server-import-maps) allows using import maps during development and testing with [@web/dev-server](https://www.npmjs.com/package/@web/dev-server) and [@web/test-runner](https://www.npmjs.com/package/@web/test-runner).
* [Deno](https://github.com/denoland/deno) is a JavaScript/TypeScript runtime with [built-in support for import maps](https://deno.land/manual/linking_to_external_code/import_maps).
* [es-module-shims](https://github.com/guybedford/es-module-shims) provides an import maps polyfill for browsers with basic ES modules support.
* [import-map-deployer](https://github.com/single-spa/import-map-deployer) is designed for updating import map files from CI
* [import-map-deployer](https://github.com/single-spa/import-map-deployer) is designed for updating import map files from CI.
* [import-map-overrides](https://www.npmjs.com/package/import-map-overrides) allows using import maps to improve development flow by pointing to local versions.
* [importly](https://www.npmjs.com/package/importly) generates an import map from a `package.json`.
* [SystemJS](https://github.com/systemjs/systemjs) provides a polyfill-like workflow for using import maps in older browsers with the System module format and `<script type="systemjs-importmap">`.
Expand Down
Loading