trunk
trunk copied to clipboard
Unable to build yew examples
Pardon the yew issue, but believe is trunk related.
I've attempted building 3 example projects, one from docs, another from examples, and my own implementation.
All result in the same error:
2022-09-18T15:26:28.673358Z INFO 📦 starting build
2022-09-18T15:26:28.674514Z INFO spawning asset pipelines
2022-09-18T15:26:28.675514Z ERROR ❌ error
error from HTML pipeline
Caused by:
0: error getting cargo metadata
1: failed to start `cargo metadata`: No such file or directory (os error 2)
2: No such file or directory (os error 2)
2022-09-18T15:26:28.677608Z INFO 📡 serving static assets at -> /static
2022-09-18T15:26:28.677644Z INFO 📡 server listening at http://127.0.0.1:8080
I have the wasm32-unknown-unknown
toolchain
$ rustup show
Default host: x86_64-unknown-linux-gnu
rustup home: /home/admin/.rustup
installed targets for active toolchain
--------------------------------------
thumbv7em-none-eabi
thumbv7em-none-eabihf
wasm32-unknown-unknown
x86_64-unknown-linux-gnu
active toolchain
----------------
stable-x86_64-unknown-linux-gnu (default)
rustc 1.62.1 (e092d0b6b 2022-07-16)
$ trunk -V
trunk 0.16.0
Running arch linux, maybe platform related? Dunno. Brand new to trunk/yew.
Did you install trunk with --locked
?
https://github.com/thedodd/trunk/blob/5fe418aacd2787fb7e5f5916b509e4f81fcb218f/src/config/manifest.rs#L20
This is the error - appears to be unable to locate your Cargo.toml file via pathing somehow. Could it be a symlink? What happens when you run cargo metadata
?
I followed the yew guide. It doesn't use the --locked
flag, so I assume no. I can try using it. cargo metadata
works and spits loads of text about the Config.toml
file
Utilizing --locked
gave me two warnings while installing
warning: package `cpufeatures v0.2.2` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
warning: package `tracing-subscriber v0.3.12` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
Attempting trunk serve
following, resulted in the same failure outcome.
Reverting (assuming initial installed without) to the install without the --locked
flag has the same outcome.
Regarding the symlink, if I understand correctly. I've tried on a mounted drive and the os drive. Same result, I think this would eliminate the possibility?
I tried serving a yew app and got the same error.. about some traits not found in the scope like Copy, Default, Clone, and some macros and some other crates not found errors. Should I share the screen shots? (BTW I'm trying this on WSL)
Sounds like a different error if it is talking about traits not found. Believe these are just from the standard prelude though. @etch1000
This only happens on my linux machine (not on my macbook), seems to be platform specific.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue was closed because it has been stalled for 5 days with no activity.
I remove exists folder '/dist' and run command 'trunk build', then it's be fine when I execute 'trunk serve'