Friendship with wasmpack ended, trunk is my new best friend

crates/mipsy_web/.gitignore

@@ -1,6 +1,4 @@
 dist/
-static/wasm.js
-static/tailwind.css
-static/wasm_bg.wasm
+tailwind.css
 Session.vim
 _static/tailwind.css

crates/mipsy_web/README.md

@@ -68,19 +68,12 @@ See [mipsy](https://github.com/insou22/mipsy/blob/main/README.md) for more infor
 ## Dependencies
 1) Install rust via rustup, by following the instructions at [rustup](https://www.rust-lang.org/tools/install)
 2) Install tailwindcss via npm `npm i -g tailwindcss`.
-3) Install cargo-watch using `cargo install cargo-watch` if you wish to serve with hot-reload. 
+3) Install trunk via the instructions on [their website](https://trunkrs.dev/)
 
 ## Development
-1) `scripts/build_dev.sh` will compile the relevant rust code to wasm files, and place into the static directory
-2) `scripts/serve.sh` will simply run a http client inside `static/` to serve the relevant files.      
-
-`scripts/hot_reload_build.sh` also exists to compile the rust code to wasm files, but will also watch for changes to the `src` directory
-
-## Production
-1) `scripts/deploy.sh` will be useful for figuring out how to compile release, build tailwind for release, and then deploy.
-
-## Debug
-If you have no CSS - you will need to produce `tailwind.css` file , `./purge_tailwind.sh` should help here. 
-
-tailwind setup with https://dev.to/arctic_hen7/how-to-set-up-tailwind-css-with-yew-and-trunk-il9
+1) `trunk serve` will compile the relevant rust code to wasm files, generate the css, chuck them into `dist/` and serve a web server.
+It will also watch files for changes, and reload. You can use `trunk serve` during development
+2) `trunk build --release` is used for deployment. It will compile optimized rust code, optimized/minified css + bundle them in `dist/`.
 
+## Deployment
+1) `scripts/deploy.sh` runs the build script, and then copies across the files to UNSW cse web servers.

crates/mipsy_web/Trunk.toml

@@ -0,0 +1,16 @@
+[build]
+# The index HTML file to drive the bundling process.
+target = "index.html"
+# Build in release mode.
+release = false
+# The output dir for all final assets.
+dist = "dist"
+# The public URL from which assets are to be served.
+public_url = "/"
+# Whether to include hash values in the output file names.
+filehash = true
+
+[[hooks]]
+stage = "build"
+command = "sh"
+command_arguments = ["-c", "mkdir -p $TRUNK_STAGING_DIR/assets; if [ $TRUNK_PROFILE = 'release' ]; then NODE_ENV=production tailwindcss -c ./tailwind.config.js -o $TRUNK_STAGING_DIR/assets/tailwind.css --minify; else tailwindcss -c ./tailwind.config.js -o $TRUNK_STAGING_DIR/assets/tailwind.css; fi"]