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
I keep getting warnings from cargo leptos (which I'm linking to through the (slightly patched) crates.io library) that wasm-opt has a new version available. Why are we downloading this tool externally, when I believe a good rust binding exists:
I believe linking to this binding would be much cleaner, avoid the need to download an external tool, and allow me to statically include more of my project without having to worry about external (i.e. non-rust library) dependencies.
On that note, this would probably have to be an experimental feature flag or something, I've been using grass (https://docs.rs/grass/latest/grass/fn.from_path.html) which is working perfectly, maybe we could statically link against this as well?
The text was updated successfully, but these errors were encountered:
I keep getting warnings from
cargo leptos
(which I'm linking to through the (slightly patched) crates.io library) thatwasm-opt
has a new version available. Why are we downloading this tool externally, when I believe a good rust binding exists:https://docs.rs/wasm-opt/latest/wasm_opt/
I believe linking to this binding would be much cleaner, avoid the need to download an external tool, and allow me to statically include more of my project without having to worry about external (i.e. non-rust library) dependencies.
On that note, this would probably have to be an experimental feature flag or something, I've been using
grass
(https://docs.rs/grass/latest/grass/fn.from_path.html) which is working perfectly, maybe we could statically link against this as well?The text was updated successfully, but these errors were encountered: