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'm unsure if this is officially supported or not, I see that the documentation is scarce for build scripts.
I was hoping to try use the wasm-pack crate as a build dependency and use it in the build script for some local automation.
I tried using the build options and commands to run the wasm build command like so.
let options = BuildOptions{path:Some(std::env::current_dir()?),scope:None,disable_dts:true,target: wasm_pack::command::build::Target::NoModules,debug:true,dev:true,out_dir:get_workspace_path()?.join("tms-client").join("web").join("pkg").to_string_lossy().to_string(),out_name:Some("rust_lib_my_app".to_string()),extra_options:vec![],
..Default::default()};let command = wasm_pack::command::Command::Build(options);
wasm_pack::command::run_wasm_pack(command)?;Ok(())
But I came into an issue where the command would seemingly execute, but freeze waiting for the file lock on the build directory
🐛 Bug description
I'm unsure if this is officially supported or not, I see that the documentation is scarce for build scripts.
I was hoping to try use the
wasm-pack
crate as a build dependency and use it in the build script for some local automation.I tried using the build options and commands to run the wasm build command like so.
But I came into an issue where the command would seemingly execute, but freeze waiting for the file lock on the build directory
And it seems to get stuck waiting for the file lock forever.
🤔 Expected Behavior
Build script generates the wasm outputs
👟 Steps to reproduce
🌍 Your environment
Include the relevant details of your environment.
wasm-pack version: 0.12.1
rustc version: 1.79.0
The text was updated successfully, but these errors were encountered: