Conversation
|
This PR modifies If appropriate, please update This PR modifies If appropriate, please update |
src/build_helper/src/npm.rs
Outdated
| cmd.arg("install"); | ||
|
|
||
| // ensure pnpm obeys the lockfile, and disable command shims so we can controll the nodejs version easily | ||
| //cmd.args(&["--config.extendNodePath=false", "--config.nodeLinker=hoisted", "--frozen-lockfile", "--shamefully-hoist"]); |
src/build_helper/src/npm.rs
Outdated
| let exit_status = cmd.spawn()?.wait()?; | ||
| if !exit_status.success() { | ||
| eprintln!("npm install did not exit successfully"); | ||
| eprintln!("pnpm install did not exit successfully"); |
src/build_helper/src/npm.rs
Outdated
| eprintln!("pnpm install did not exit successfully"); | ||
| return Err(io::Error::other(Box::<dyn Error + Send + Sync>::from(format!( | ||
| "npm install returned exit code {exit_status}" | ||
| "pnpm install returned exit code {exit_status}" |
bootstrap.example.toml
Outdated
| # The npm executable to use. Note that this is used for rustdoc-gui tests, | ||
| # otherwise this can be omitted. | ||
| # The pnpm executable to use. Note that this is used for rustdoc-gui tests and | ||
| # tidy js extra-checks, otherwise this can be omitted. | ||
| # | ||
| # Under Windows this should be `npm.cmd` or path to it (verified on nodejs v18.06), or | ||
| # Under Windows this should be `pnpm.cmd` or path to it (verified on nodejs v18.06), or | ||
| # error will be emitted. | ||
| #build.npm = "npm" | ||
| #build.pnpm = "pnpm" |
This comment has been minimized.
This comment has been minimized.
dd4b4c9 to
b5bcc0e
Compare
|
Removed all the references to pnpm, I think tidy still references will also update change_tracker once CI is done. |
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
☔ The latest upstream changes (presumably #148721) made this pull request unmergeable. Please resolve the merge conflicts. |
do you have a link to more information about this? did it cause breakage that i could look at? |
|
Essentially #t-infra > CI keeps failing because of npm error @ 💬 and this. If you depend on a git dependency with npm, it will unconditionally do |
Use `yarn` instead of `npm` for JS/TS dependencies Building on `@lolbinarycat` 's excellent work ( #148672 ). `npm` apparently has certain edge-cases where it doesn't actually respect the lockfile it's fed, which has led to at least one [CI breakage](https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/CI.20keeps.20failing.20because.20of.20npm.20error/near/554420543). `yarn` seems to not suffer from those same issues, and also has a `--frozen` flag for its `install` command
Use `yarn` instead of `npm` for JS/TS dependencies Building on `@lolbinarycat` 's excellent work ( rust-lang/rust#148672 ). `npm` apparently has certain edge-cases where it doesn't actually respect the lockfile it's fed, which has led to at least one [CI breakage](https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/CI.20keeps.20failing.20because.20of.20npm.20error/near/554420543). `yarn` seems to not suffer from those same issues, and also has a `--frozen` flag for its `install` command
|
#148763 has been merged, closing this. |
npm lockfile implementation is nonfunctional