Incompatible with Rust 1.83.0

[kjxbyz]

> which wasm-pack (pwd: null, env: null)
/Users/ying/.cargo/bin/wasm-pack
> cargo read-manifest (pwd: rust, env: null)
> wasm-pack build -t no-modules -d /Users/ying/my_app/web/pkg --no-typescript --out-name rust_lib_my_app rust -- -Z build-std=std,panic_abort (pwd: null, env: {RUSTUP_TOOLCHAIN: nightly, RUSTFLAGS: -C target-feature=+atomics,+bulk-memory,+mutable-globals, CARGO_TERM_COLOR: always})
Error: `cargo metadata` exited with an error: error: failed to parse lock file at: /Users/ying/my_app/rust/Cargo.lock

Caused by:
  lock file version 4 requires `-Znext-lockfile-bump`

Caused by: `cargo metadata` exited with an error: error: failed to parse lock file at: /Users/ying/my_app/rust/Cargo.lock

Caused by:
  lock file version 4 requires `-Znext-lockfile-bump`

Unhandled exception:
ProcessException: Bad exit code (1). stderr=Error: `cargo metadata` exited with an error: error: failed to parse lock file at: /Users/ying/my_app/rust/Cargo.lock

Caused by:
  lock file version 4 requires `-Znext-lockfile-bump`

Caused by: `cargo metadata` exited with an error: error: failed to parse lock file at: /Users/ying/my_app/rust/Cargo.lock

Caused by:
  lock file version 4 requires `-Znext-lockfile-bump`


  Command: wasm-pack build -t no-modules -d /Users/ying/my_app/web/pkg --no-typescript --out-name rust_lib_my_app rust -- -Z build-std=std,panic_abort
#0      runCommand (package:flutter_rust_bridge/src/cli/run_command.dart:67:5)
<asynchronous suspension>
#1      _executeWasmPack (package:flutter_rust_bridge/src/cli/build_web/executor.dart:154:3)
<asynchronous suspension>
#2      executeBuildWeb (package:flutter_rust_bridge/src/cli/build_web/executor.dart:70:3)
<asynchronous suspension>
#3      BuildWebCommand.run (package:flutter_rust_bridge/src/cli/build_web/entrypoint.dart:18:5)
<asynchronous suspension>
#4      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#5      main (file:///Users/ying/.pub-cache/hosted/pub.dev/flutter_rust_bridge-2.7.0/bin/flutter_rust_bridge.dart:8:3)
<asynchronous suspension>
Error: Fail to execute command, please see logs above for details.

[fzyzcjy]

Hmm, could you please try to run cargo metadata command and see whether it errors?

[kjxbyz]

metadata.json

[fzyzcjy]

Interesting... Given that it says wasm-pack build -t no-modules -d /Users/ying/my_app/web/pkg --no-typescript --out-name rust_lib_my_app rust -- -Z build-std=std,panic_abort errors, could you please run this command directly in shell and see whether it errors?

[kjxbyz]

ying@Kimmys-iMac my_app % wasm-pack build -t no-modules -d /Users/ying/my_app/web/pkg --no-typescript --out-name rust_lib_my_app rust -- -Z build-std=std,panic_abort
[INFO]: 🎯  Checking for the Wasm target...
info: downloading component 'rust-std' for 'wasm32-unknown-unknown'
info: installing component 'rust-std' for 'wasm32-unknown-unknown'
 18.9 MiB /  18.9 MiB (100 %)  15.0 MiB/s in  1s ETA:  0s
[INFO]: 🌀  Compiling to Wasm...
error: the `-Z` flag is only accepted on the nightly channel of Cargo, but this is the `stable` channel
See https://doc.rust-lang.org/book/appendix-07-nightly-rust.html for more information about Rust release channels.
Error: Compiling your crate to WebAssembly failed
Caused by: Compiling your crate to WebAssembly failed
Caused by: failed to execute `cargo build`: exited with exit status: 101
  full command: cd "rust" && "cargo" "build" "--lib" "--release" "--target" "wasm32-unknown-unknown" "-Z" "build-std=std,panic_abort"

[fzyzcjy]

Hmm, if wasm-pack fails, then looks like something related to that package instead of frb core. Maybe we can create an issue and ask there

[kjxbyz]

rustwasm/wasm-pack#1456

[kjxbyz]

Why is the value of RUSTUP_TOOLCHAIN ​​nightly?

flutter_rust_bridge_codegen build-web
> which wasm-pack (pwd: null, env: null)
/Users/ying/.cargo/bin/wasm-pack
> cargo read-manifest (pwd: rust, env: null)
> wasm-pack build -t no-modules -d /Users/ying/my_app/web/pkg --no-typescript --out-name rust_lib_my_app --dev rust -- -Z build-std=std,panic_abort (pwd: null, env: {RUSTUP_TOOLCHAIN: nightly, RUSTFLAGS: -C target-feature=+atomics,+bulk-memory,+mutable-globals, CARGO_TERM_COLOR: always})

[fzyzcjy]

IIRC because we need some nighly flags to compile to web. But don't be afraid by the name "nightly" - it is quite stable. I also asked "hey nightly seems too dangerous should I use it in production" years ago, but iirc the answer is "it is quite safe".