use virtual module prefix to play nice with other plugins

[Rich-Harris]

Notwithstanding our separate conversations about consolidating some of the node- plugins, I just ran into an issue while trying to fix rollup/rollup-plugin-commonjs#90, which is that other plugins might try to resolve IDs like __filename depending on the plugin order (and in the case of rollup-plugin-node-resolve, that blows up).

The 'convention' (albeit not very well documented etc) with other plugins that use virtual modules is to prefix module IDs with \0, or even \0mypluginname: – this prevents other plugins from trying to resolve those IDs (the logic is built into createFilter, for example). \0 works because it's not a legal character in file names.

[calvinmetcalf]

we should probaby name space this just in case

[calvinmetcalf]

probaby makes sense to name space it, otherwise seems like a good ides

[Rich-Harris]

done 👍

[calvinmetcalf]

thanks published as 1.0.8

[kuraga]

The 'convention' (albeit not very well documented etc) with other plugins that use virtual modules is to prefix module IDs with \0

@Rich-Harris , could you remember, please, where this convention is introduced and documented? Because now we have #23 and #18 .