Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support new URL("./image.png", import.meta.url) Asset modules

See original GitHub issue

Webpack 5 support new URL("./image.png", import.meta.url) as asset modules.

Can vite support it?

Issue Analytics

State:
Created 3 years ago
Reactions:3
Comments:10 (5 by maintainers)

Top GitHub Comments

1reaction

sodateacommented, Jul 15, 2021

Supported since v2.4 https://github.com/vitejs/vite/commit/4cbb40d2f1a4050c9944e7e1d9e0f5b204b7e37b

1reaction

jiangfengmingcommented, Jan 27, 2021

@jiangfengming What’s difference with @web/rollup-plugin-import-meta-assets?

example: https://modern-web.dev/docs/building/rollup-plugin-import-meta-assets/#examples

That plugin just doesn’t work with vite.

If put it into plugins field, the code would be transformed into new URL(import.meta.ROLLUP_FILE_URL_1, import.meta.url), but import.meta.ROLLUP_FILE_URL_1 is undefined at runtime.

If put it into build.rollupOptions.plugins section, the generated code would be something like new URL(new URL("foo.688baecb.png",t.url).href,t.url)', but t.url(import.meta.url) is undefined` in production build. So it will fail to construct URL because lack of origin.

And @web/rollup-plugin-import-meta-assets doesn’t obey build.assetsInlineLimit option.