Respect import maps

[lubomirblazekcz]

Is your feature request related to a problem? Please describe.
Currently it's not possible to use importmaps with Vite, because vite resolves all node_modules by default. So if I would want to use import maps with modules on cdn, rather then node_modules, I cannot.

Describe the solution you'd like
Easy on/off switch, resolve.node false

I know main advantage of Vite is transforming node_modules, but having option to also use benefits of using esm modules from cdn with importmaps is also great.

[yyx990803]

I think the better way to deal with this is to respect import maps when parsing index.html and avoid rewriting URLs listed in the import map.

Also, if you want to import from CDNS, you can use alias and point them to CDN urls instead of using import maps for now. FYI Import maps currently only works in latest version of Chrome, while Vite aliases will work for all browsers when built.

[lubomirblazekcz]

It can be easily polyfilled with https://www.npmjs.com/package/es-module-shims though, but I agree Vite aliases might be better for production. But Vite respecting the import maps would be also great.

[lubomirblazekcz]

For anyone interested in using importmaps with Vite right now, you can with workaround. When es-module-shims polyfill is used with type="importmap-shim" and type="module-shim", all the imports will be handled with the shim.

[maicol07]

@lubomirblazekcz I've tried the polyfill but it doesn't work with the dev server since the analyzer plugin throws an error:

[plugin:vite:import-analysis] Failed to resolve import "modulePage" from "resources\js\app.js". Does the file exist?
C:/Users/Maicol/Documents/Progetti/Web/osm_rewrite/resources/js/app.js:6:50
4  |  
5  |  // eslint-disable-next-line import/no-unresolved
6  |  import /* @vite-ignore */ * as modulePages from 'modulePage';
   |                                                   ^
7  |  
8  |  import '../scss/app.scss';
    at formatError (C:\Users\Maicol\Documents\Progetti\Web\osm_rewrite\node_modules\.pnpm\vite@2.5.1\node_modules\vite\dist\node\chunks\dep-972722fa.js:51153:46)
    at TransformContext.error (C:\Users\Maicol\Documents\Progetti\Web\osm_rewrite\node_modules\.pnpm\vite@2.5.1\node_modules\vite\dist\node\chunks\dep-972722fa.js:51149:19)
    at normalizeUrl (C:\Users\Maicol\Documents\Progetti\Web\osm_rewrite\node_modules\.pnpm\vite@2.5.1\node_modules\vite\dist\node\chunks\dep-972722fa.js:74554:26)
    at async TransformContext.transform (C:\Users\Maicol\Documents\Progetti\Web\osm_rewrite\node_modules\.pnpm\vite@2.5.1\node_modules\vite\dist\node\chunks\dep-972722fa.js:74687:57)
    at async Object.transform (C:\Users\Maicol\Documents\Progetti\Web\osm_rewrite\node_modules\.pnpm\vite@2.5.1\node_modules\vite\dist\node\chunks\dep-972722fa.js:51354:30)
    at async transformRequest (C:\Users\Maicol\Documents\Progetti\Web\osm_rewrite\node_modules\.pnpm\vite@2.5.1\node_modules\vite\dist\node\chunks\dep-972722fa.js:67098:29)
    at async viteTransformMiddleware (C:\Users\Maicol\Documents\Progetti\Web\osm_rewrite\node_modules\.pnpm\vite@2.5.1\node_modules\vite\dist\node\chunks\dep-972722fa.js:67225:32

[canadaduane]

For anyone interested in using importmaps with Vite right now, you can with workaround. When es-module-shims polyfill is used with type="importmap-shim" and type="module-shim", all the imports will be handled with the shim.

This is true, but it has the unfortunate side-effect that code inside a regular module script tag can't access code inside the importmap-shim script tag. Unless you've found a way that they can talk?

[dutchcelt]

Does anybody know if there's any progress on this?