April 22, 2026 - An import map is a JSON object that allows developers to control how the browser resolves module specifiers when importing JavaScript modules. It provides a mapping between the text used as the module specifier in an import statement or import() operator, and the corresponding value that will ...

July 25, 2022 - Import maps makes it possible to use bare module specifiers in the browser without depending on the complicated build systems currently prevalent in the JavaScript ecosystem, but it is not widely supported in web browsers at the moment.

June 16, 2025 - ES2020 introduced dynamic import() natively. Combined with import maps, you can now achieve scoped, on-demand module loading directly in the browser—without a bundler.

October 24, 2024 - A modern way to use JavaScript modules is with the script type="importmap" tag. This lets you to define a mapping of external module names to their corresponding URLs, making it easier to include and use external modules in your code.

March 28, 2023 - They are supported by modern browsers and provide several benefits over older, non-modular approaches to JavaScript development. A modern way to use ES modules is with the <script type="importmap"> tag. This tag allows you to define a mapping of external module names to their corresponding ...

December 20, 2024 - But what if we could easily manage our dependencies? Enter Import Maps, a native browser specification that lets you control JavaScript module loading without the need for bundling tools.

February 26, 2025 - Former home of import maps (now merged into HTML). Contribute to WICG/import-maps development by creating an account on GitHub.

May 28, 2025 - Import maps are great for both performance and developer experience, but their original limitations made them hard to use, especially at Shopify’s scale. We stepped up and pushed changes across the HTML spec, Chromium and WebKit to fix these issues at the web platform level. Now, developers can interleave JavaScript modules and multiple import maps on their HTML pages without worrying about correctness issues.

July 25, 2025 - Import maps are a way of controlling which url to download javascript modules from. The import-map-overrides library allows you to dynamically change the url for javascript modules by storing overrides in local storage.

February 23, 2023 - Import maps are designed to reduce the friction of resolving module specifiers between different Javascript runtimes like Node.js and browsers. It not only saves us from using bundlers like webpack or Babel but also gives us the ergonomics of bare specifiers while ensuring that the security properties of URLs are preserved.

May 10, 2023 - pip install download-esm download-esm @observablehq/plot This downloads the ESM version of Observable Plot from the jsDelivr CDN, figures out its dependencies, downloads them as well (40 files total!) and rewrites their imports to be local, not CDN paths · More details here: https://simon...

Import maps are a new feature designed to allow browsers to use the same type of import specifiers as Node, where the first character is not a “.” or “/”. They can also be used to remap any import path to something else.

How to use Rails without the need for a Node.js, Yarn, or a JavaScript bundler. How to create a new Rails application using import maps, Bun, esbuild, Rollup, or Webpack to bundle your JavaScript.

May 30, 2023 - The JavaScript ecosystem has evolved ... Maps is the latest advancement, a technique to make managing and consuming EcmaScript modules (ESM) much more straightforward for client-side developers....

June 26, 2023 - Import maps are a fantastic way to simplify the way we work with JavaScript modules in the browser. They make it easier to manage dependencies, update individual modules, and use multiple versions of the same package.

January 14, 2022 - First, I used HEY as the testbed to validate the aspiration for import maps to become the default path in Rails 7. This is the benefit of using new tech in anger: You discover all the gaps between exuberant theory and actual practice. Second, after proving that import maps work well on the web, we turned our eye to reworking several aspects of the Turbo Native integration. Especially dealing with the timing difference of loading all JavaScript after DOMContentLoaded.

November 22, 2023 - This might not sound too useful until you remember that, y’know, browsers still support non-module JavaScript. This means it’s possible to modify the import map in the browser using client-side JavaScript, in response to the features you detect, settings you retrieve (using localStorage, ...

January 10, 2023 - JavaScript import maps are now supported cross-browser · r/javascript • · r/javascript · Chat about javascript and javascript related projects. Yes, typescript counts. Please keep self promotion to a minimum/reasonable level. Weekly visitors · Weekly contributions ·

March 2, 2023 - Let’s explain the terms first. The string literal "app.mjs" in the above examples is called a Module Specifier in ECMAScript, and the map which maps "app.mjs" to a URL is called a Module Specifier Map. An import map is an object with two optional items:

class ImportMap class Configuration def initialize @imports = [] @modules = Set.new end def import(name, **options) dep_alias, include_subpackages = options.values_at(:alias, :include_subpackages) version = package_version(name) @imports << { name:, version:, remote: remote_specifier(name, version, dep_alias:) } return unless include_subpackages slash_name = "#{name}/" @imports << { name: slash_name, version:, remote: remote_specifier(name, version, dep_alias:, slash: true) } end def module(name) @modules.add(name) end def mount_directory(folder, recursive: false) root_path = Rails.root.join('