Skip to content

Install latest npm when building #4035

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AbhitejJohn merged 4 commits into from
Sep 9, 2025
Merged

Install latest npm when building #4035

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
aad3e1f
Install latest npm when building
JoeRobich Sep 8, 2025
85c20b9
Install npm 11.6.0
JoeRobich Sep 8, 2025
9bfbab3
Log npm versions when installing
JoeRobich Sep 8, 2025
f4ca91f
Break up npm install into multiple steps
JoeRobich Sep 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions eng/templates/build-and-test-tasks.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,10 +13,8 @@ steps:
inputs:
versionSpec: $(NodeJSVersion)

# This work around NPM issue https://github.com/npm/cli/issues/8468
# This issue should be resolved when v11.5.3 is released
- script: npm install -g [email protected]
displayName: Downgrade npm to v11.4.1
- script: npm install -g npm
displayName: Install latest npm
Copy link
Contributor

@jonsequitur jonsequitur Sep 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tend to prefer installing a specific version. If a new version comes out and something in our build breaks as a result, it won't be obvious what changed.

Copy link
Member Author

@JoeRobich JoeRobich Sep 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated. Looking at the dotnet-public-npm feed the 11.4.1 version I was previously downgrading to was not part of the feed, perhaps that is why we were still seeing the error despite downgrading. I made sure 11.6.0 was pushed to the feed.


- script: |
robocopy "eng\resources" "$(Build.SourcesDirectory)\artifacts"
Expand Down