Use dependency output wasm in cargo build #128
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
概要
#127 で
wasm-opslang
crate 内でビルドした wasm ファイルなどをdevtools-frontend
のcargo build
内で使う変更の意図や背景
cargo package
のとき、ソースディレクトリ内にCargo.toml
が存在すると問答無用でコピー対象から外れてしまう(Setup NodeJS 21 in Rust workflows for integrated frontend build #120 )devtools-frontend
crate 内で wasm の crate をビルドするのは無理があるwasm-opslang
crate 内で wasm のビルドまでを行い、$OUT_DIR
に出力するようにしたwasm-opslang
crate 内でビルドした wasm ファイルなどをdevtools-frontend
crate のbuild.rs
内で vite から扱えるディレクトリ構造にコピーして使うdevtools-frontend
crate 内でwasm-pack build
をする必要が無くなったため、そのロジックを削除発端となる Issue