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
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:
If your plugin uses 'virtual modules' (e.g. for helper functions), prefix the module ID with \0. This prevents other plugins from trying to process it.
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?
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).
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: