My first vite plugin, so take that into account before using.
- virtual/vue-bevy/generated_wasms: List of generated crates
There are 2 vite plugins I tried before starting my own.
I did get both working, rsw seems more complicated than was needed, the other didn't do as much, and neither used vite well, and both required manual steps, though both did work
- Evan You interview - This interview was so helpful in understanding vite use of node modules resolution system, its dated but is making me rethink how important node modules are so vite can do more
Other references
If you are new to rust and wasm, you kinda need to learn what each of the following do:
- wasm-pack
- wasm-bindgen
- wasm-bindgen-cli
- wasm-opt
For our use case, we are basically passing config options though 3 abstractions layers before anything useful happens because I don't care about publishing wasms on npm. Those options are:
--out-dir: where cargo build the file
--out-name: what you told cargo build call it
--profile: dev | release | profiling
--target web
I found this after learning most of this the hard way Work With Wasm-bindgen for an overview. I disagree on author on one point though, I don't care about npm functionality because we can just tell vite where the files.
Requires wasm-bindgen-cli
cargo install -f wasm-bindgen-cli