Support for assets from node_modules and import.meta.url?

[michaelfranzl]

Hi!

I have a module mymodule in node_modules with the following file structure:

node_modules/mymodule
├── lib
│   ├── lib.js
│   ├── lib.svg
├── package.json
└── main.js

Inside lib.js I use import.meta.url to calculate the absolute path to lib.svg. This is necessary because I need to fetch the contents of the SVG file to parse it, and as paths are always page-relative, and not file-relative, there seems to be no other way. This technique seems to be directly supported 1 and it indeed works natively in the browser (plain ES6, without running any transformations, like bundling or packaging).

Now, from that, snowpack build generates the following file structure:

...
├── _snowpack
...
│   └── pkg
│       └── mymodule.js

But, lib.svg is ignored and missing.

I put mymodule/lib/lib.svg into knownEntrypoints, but the build command still does not install the file into the build directory.

Does Snowpack support this use case? How can I get at lib.svg when running snowpack dev as well as snowpack build?

Thanks!

[michaelfranzl]

ping