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
If you notice theres no hashed "public/esbuilds-builds/assets/academic-cap-[hash].svg", it only has the ".js" entrypoint. I'm curious if it would be possible to support the use-case of keeping a referenced to the hashed-file with the original extension and not the generated JS file.
The text was updated successfully, but these errors were encountered:
I looked into this a bit. For my own reference, here's a more concrete example:
entry.js:
console.log(import("./academic-cap.svg"))
academic-cap.svg:
<svg/>
When the above files are bundled with esbuild entry.js --bundle --format=esm --splitting --outdir=out --metafile=meta.json --loader:.svg=file, I get the following meta.json file:
This information lets you map from out/entry.js => out/academic-cap-JHXDOPWG.js => academic-cap.svg but there is no link to out/academic-cap-55CCFTCE.svg (the file referenced by the imported string).
The title is hard to understand, but basically im looking for a map back to the original file that creates an asset chunk.
Example:
in my ESBuild metafile:
If you notice theres no hashed
"public/esbuilds-builds/assets/academic-cap-[hash].svg"
, it only has the ".js" entrypoint. I'm curious if it would be possible to support the use-case of keeping a referenced to the hashed-file with the original extension and not the generated JS file.The text was updated successfully, but these errors were encountered: