-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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.
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
[BUG] npm ci fails on Windows with Node.js 22.0.0 #7417
Labels
Comments
westy92
added
Bug
thing that needs fixing
Needs Triage
needs review for next steps
Release 10.x
labels
Apr 25, 2024
westy92
changed the title
[BUG] <title>
[BUG] npm ci fails on Windows with Node.js 22.0.0
Apr 25, 2024
zloirock
added a commit
to zloirock/core-js
that referenced
this issue
Apr 25, 2024
This looks to be a problem with the node installation itself. This is being tracked at nodejs/node#52682 |
Reopening since this will require a fix in npm. |
lukekarrys
added a commit
that referenced
this issue
Apr 25, 2024
lutzroeder
added a commit
to lutzroeder/netron
that referenced
this issue
Apr 27, 2024
lutzroeder
added a commit
to lutzroeder/netron
that referenced
this issue
Apr 27, 2024
lukekarrys
added a commit
that referenced
this issue
Apr 29, 2024
lutzroeder
added a commit
to lutzroeder/netron
that referenced
this issue
May 3, 2024
lutzroeder
added a commit
to lutzroeder/netron
that referenced
this issue
May 3, 2024
lutzroeder
added a commit
to lutzroeder/netron
that referenced
this issue
May 3, 2024
lutzroeder
added a commit
to lutzroeder/netron
that referenced
this issue
May 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
On Windows,
npm ci
fails.(Note: this works fine on Linux and macOS)
https://github.com/westy92/holiday-event-api-js/actions/runs/8827184894/job/24234452752
Expected Behavior
npm ci
succeedsSteps To Reproduce
npm ci
Environment
; copy and paste output from `npm config ls` here
The text was updated successfully, but these errors were encountered: