Spencer C. Imbleau

> Could someone help me understand why defining a new profile that sets the needed fields is not sufficient? **How might one do this with profiles?** I think most of...

Well that certainly satisfies me. Didn't know that was possible.

One issue with this actually still exists @epage : ``` warning: profiles for the non root package will be ignored, specify profiles at the workspace root: package: /Users/simbleau/git/nova/client/Cargo.toml workspace: /Users/simbleau/git/nova/Cargo.toml...

Please!

Best to do these steps in a GitHub Action triggered on a "v*" release. This is what I do to publish packages, e.g. https://github.com/vectorgameexperts/bevy-async-task/blob/main/.github/workflows/release.yml

Sure!

Maybe solution is to not use wasm-pack and instead opt for using cargo, so that the `PROFILE` and other environment variables can be set outside of trunk. Hence, the onus...

> Another alternative would be to add some `--cargo-profile` flag, which can override the cargo profile ad-hoc. That would do the trick, would be quick, but not the best/ideal way....

Is this only for WASM?

This sounds low priority since it is a network renegotiation under rare circumstances to increase performance, not to solve a severe problem in connectivity. Good find.