You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been working on vite-plugin-jspm and I was trying to control the dependencies using export maps and JSPM!
And what I wanted to achieve is that I wanted plain externalized IDs (dependency) like { id: 'react-dom', external: true }! and not something that Vite handles (with external, we get some control, but Vite still injects /@id/ to the externalized id) here.
Expected behaviour
As far as I think, we've got two expected behaviours:
adding an option along external, that let vite know that a specific id should not be prefixed with /@id/
Or not prefixing the ids that have external as true!
I prefer the second one though I'm not sure if that has to do with external
Example
Since es-module-shims cannot figure out what /@id/react is, we get this error:
GET http://localhost:3000/@id/react net::ERR_ABORTED 404 (Not Found)
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
Describe the bug
I've been working on vite-plugin-jspm and I was trying to control the dependencies using export maps and JSPM!
And what I wanted to achieve is that I wanted plain externalized IDs (dependency) like
{ id: 'react-dom', external: true }
! and not something that Vite handles (with external, we get some control, but Vite still injects/@id/
to the externalized id) here.Expected behaviour
As far as I think, we've got two expected behaviours:
external
, that let vite know that a specific id should not be prefixed with/@id/
external
as true!I prefer the second one though I'm not sure if that has to do with
external
Example
Since es-module-shims cannot figure out what
/@id/react
is, we get this error:Reproduction
Nothing to reproduce!
System Info
Used Package Manager
pnpm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: