-
-
Notifications
You must be signed in to change notification settings - Fork 130
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
Virtual Svelte module ids should start with \0
#274
Comments
I feel that it's best for integrations to be able to process virtual modules. As in this case, our virtual module is mean to be processed by other plugins (we serve raw components). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
This tool creates virtual modules for svelte, which can cause problems for other plugins which attempt to load those files, not realizing they are virtual. The plugin documentation for rollup specifies:
So, should virtual modules created when unplugin-icons is configured with
compiler: "svelte"
be prefixed? Or is there another way that other plugins should detect these are virtual modules, ideally without hitting the filesystem?See storybookjs/storybook#20562 for the issue in Storybook.
Reproduction
https://github.com/enyo/storybook-test/tree/main/my-app
System Info
Used Package Manager
npm
Validations
The text was updated successfully, but these errors were encountered: