Registry / web-framework / vite-import-maps

vite-import-maps

library0.2.6jsnpmunverified

Vite plugin that generates and manages browser import maps for shared dependencies in Vite applications, targeting micro-frontends, plugin systems, and runtime ESM loading. Current stable version is 0.2.6, with monthly patch releases. Key differentiators: supports CommonJS modules via static analysis, injects import map directly into HTML or emits as a standalone file, provides Subresource Integrity (SRI) hashes, and handles both npm packages and local entry modules. Requires Vite >=6.0.0, rollup >=4.0.0, or rolldown >=1.0.0-rc.0. Renamed from 'vite-plugin-native-import-maps' in v0.2.0.

web-framework http-networking

npm install vite-import-maps

github ↗package ↗

INSTALL

IMPORT

SIG · VITE-IMPORT-MAPS

vite-import-maps

web-frameworkjavascriptv0.2.6

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–223 runs

build_error

glibc

node 18–223 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

viteImportMaps

✓ import { viteImportMaps } from 'vite-import-maps'

✗ import viteImportMaps from 'vite-import-maps'

Named export, not default. Named export was renamed from 'vitePluginNativeImportMaps' in v0.2.0.

viteImportMaps (default)

✓ import viteImportMaps from 'vite-import-maps'

✗ import { viteImportMaps } from 'vite-import-maps'

Since v0.2.0, a default export is also available; both work. However, the named export is recommended for explicit usage.

Types (PluginOptions)

✓ import type { PluginOptions } from 'vite-import-maps'

✗ import { PluginOptions } from 'vite-import-maps'

Type-only import to avoid runtime inclusion.

CommonJS require

✓ const { viteImportMaps } = require('vite-import-maps')

✗ const viteImportMaps = require('vite-import-maps')

CJS requires destructuring because the package exports both named and default. This works if your project uses CJS.

Old named export (deprecated)

✓ import { vitePluginNativeImportMaps } from 'vite-import-maps'

✗ import { vitePluginNativeImportMaps } from 'vite-plugin-native-import-maps'

The plugin was renamed in v0.2.0. Old import path 'vite-plugin-native-import-maps' no longer exists; use 'vite-import-maps'.

Virtual module

✓ import importMap from 'virtual:importmap'

✗ import importMap from 'vite-import-maps/virtual:importmap'

The virtual module is provided by the plugin; no file path needed. Use when injectImportMapsToHtml is false.

Sets up vite-import-maps to expose 'react' and 'react-dom' via browser import maps with SRI integrity and logging enabled.

// vite.config.ts import { defineConfig } from 'vite'; import { viteImportMaps } from 'vite-import-maps'; export default defineConfig({ plugins: [ viteImportMaps({ imports: ['react', 'react-dom'], integrity: 'sha384', log: true, }), ], });

Debug

Known issues

breakingIn v0.2.0, the plugin was renamed from 'vite-plugin-native-import-maps' to 'vite-import-maps' and the main export was renamed from 'vitePluginNativeImportMaps' to 'viteImportMaps'.

fix

Update package name to 'vite-import-maps' and import { viteImportMaps } instead of { vitePluginNativeImportMaps }.

affects: <0.2.0

breakingRequires Vite >=6.0.0 (or Vite 7/8) as a peer dependency. Older Vite versions are not supported.

fix

Upgrade Vite to version 6.0.0 or later. For Vite 5 projects, stay on an older version or use a different plugin.

affects: >=0.2.6

deprecatedThe 'outputAsFile' option may change in future versions. It is currently stable but not guaranteed to remain.

fix

Monitor changelog for updates; alternative: use 'injectImportMapsToHtml: false' and import the virtual module.

affects: >=0.2.0

gotchaCommonJS module resolution uses static analysis via node/cjs-module-lexer; some CJS modules may not be detected correctly if they have side effects or dynamic exports.

fix

Ensure CJS modules have stable named exports. For problematic modules, use a custom entry with explicit export mapping.

affects: >=0.2.4

gotchaWhen 'injectImportMapsToHtml' is false, you must manually import the virtual module 'virtual:importmap' and inject the script tag yourself.

fix

Add <script type="importmap">{{importMapContent}}</script> to your HTML template.

affects: >=0.2.0

Errors

Common errors & fixes

Error: Cannot find module 'vite-plugin-native-import-maps'

Package was renamed to 'vite-import-maps' in v0.2.0.

fix

Run 'npm install vite-import-maps --save-dev' and update imports to use 'vite-import-maps'.

TypeError: vitePluginNativeImportMaps is not a function

Export renamed to 'viteImportMaps' in v0.2.0.

fix

Change import to '{ viteImportMaps }' from 'vite-import-maps'.

Error: Unexpected token on import map JSON (e.g., missing quotes)

Improperly formatted import map entries; likely a custom entry with invalid JSON.

fix

Ensure entries in the 'imports' array are valid strings or objects with 'name' and 'entry' properties.

Upgrade

Version history

0.2.6latest on npm

Audit

Dependencies

viterequiredCore peer dependency; plugin relies on Vite's plugin API and hooks.

rollupoptionalRequired for build-time module resolution (rollup is Vite's bundler for production builds).

rolldownoptionalAlternative bundler peer dependency for build-time module resolution (used by Vite 7+).

Agent activity

13 hits · last 30 days

node

Amazon

OpenAI (training)

Resources

githubhttps://github.com/riccardoperra/vite-import-maps ↗

packagehttps://www.npmjs.com/package/vite-import-maps ↗