This is a tracking issue from #27208 (comment).
wasm-bindgen outputs directly to a snippets folder for external inline code snippets, but does not optimize these into the single JS file itself. As a result this folder must be copied with the wasm-bindgen output files.
These are distinct from Emscripten-style inline code because they assume module syntax like an ES module file themselves - supporting import 'dep' and using their export interface as the snippet interface.
In future two possible optimizations could arise here:
- Emscripten doing the single-file JS optimization to inline these static known imports
- wasm-bindgen adding support for this optimization itself
In either of these cases, copying the snippets directory to support inline code would no longer be need which this tracks.
This is a tracking issue from #27208 (comment).
wasm-bindgen outputs directly to a snippets folder for external inline code snippets, but does not optimize these into the single JS file itself. As a result this folder must be copied with the wasm-bindgen output files.
These are distinct from Emscripten-style inline code because they assume module syntax like an ES module file themselves - supporting
import 'dep'and using theirexportinterface as the snippet interface.In future two possible optimizations could arise here:
In either of these cases, copying the snippets directory to support inline code would no longer be need which this tracks.