Skip to content

Conversation

@jtbandes
Copy link

@jtbandes jtbandes commented Jul 2, 2025

I got the following error when installing 4.0.0 with yarn:

# This file contains the result of Yarn building a package (node-crc@npm:4.0.0)
# Script name: install

...

error: the `cargo::` syntax for build script output instructions was added in Rust 1.77.0, but the minimum supported Rust version of `node-crc v4.0.0 (.../node_modules/node-crc)` is 1.65.
Switch to the old `cargo:rerun-if-env-changed=NAPI_DEBUG_GENERATED_CODE` syntax (note the single colon).
See https://doc.rust-lang.org/cargo/reference/build-scripts.html#outputs-of-the-build-script for more information about build script outputs.
warning: build failed, waiting for other jobs to finish...
�[31m�[1mInternal Error�[22m�[39m: Command failed: cargo build --release
    at genericNodeError (node:internal/errors:983:15)
    at wrappedFn (node:internal/errors:537:14)
    at checkExecSyncError (node:child_process:882:11)
    at Object.execSync (node:child_process:954:15)
    at BuildCommand.<anonymous> (.../node_modules/@napi-rs/cli/scripts/index.js:11529:30)
    at Generator.next (<anonymous>)
    at .../node_modules/@napi-rs/cli/scripts/index.js:3526:69
    at new Promise (<anonymous>)
    at __awaiter$1 (.../node_modules/@napi-rs/cli/scripts/index.js:3522:10)
    at BuildCommand.execute (.../node_modules/@napi-rs/cli/scripts/index.js:11299:16)

This seems to be fixed by changing the rust-version to 1.77 as mentioned in the error message.

jtbandes added a commit to foxglove/crc that referenced this pull request Jul 2, 2025
Includes patch to work around node-crc build issue: magiclen/node-crc#18
jtbandes added a commit to foxglove/crc that referenced this pull request Jul 3, 2025
### Changelog
None

### Docs

None

### Description

Closes #215 
Includes patch to work around node-crc build issue:
magiclen/node-crc#18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant