-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Issues: npm/cli
npm ci
validates package-lock.json
and could fail to resolve
#5113
by fritzy
was closed Jun 30, 2022
Closed
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[BUG] related to `npm install`
Documentation
documentation related issue
Needs Discussion
is pending a discussion
Priority 2
secondary priority issue
Release 7.x
work is associated with a specific npm 7 release
Release 8.x
work is associated with a specific npm 8 release
npm install -g
doesn't install local dependencies in v7
cmd:install
#2968
opened Mar 25, 2021 by
mikeharder
[BUG] Switching back to npm 6 from npm 7 results in install error
Bug
thing that needs fixing
cmd:install
related to `npm install`
config: lockfile
Priority 2
secondary priority issue
Release 7.x
work is associated with a specific npm 7 release
Release 8.x
work is associated with a specific npm 8 release
#3103
opened Apr 19, 2021 by
s2danii
[BUG] npm install --package-lock-only on optional dependencies causes package-lock.json to change
Bug
thing that needs fixing
cmd:install
related to `npm install`
config: lockfile
Priority 2
secondary priority issue
Release 8.x
work is associated with a specific npm 8 release
#4375
opened Feb 4, 2022 by
peterbe
2 tasks done
[BUG] unexpected overriding peer dependency happen on incremental install
Bug
thing that needs fixing
cmd:install
related to `npm install`
Priority 2
secondary priority issue
Release 8.x
work is associated with a specific npm 8 release
#4419
opened Feb 16, 2022 by
dr-js
2 tasks done
[BUG] npm treat every path from gitlab as git url even it is a dist path to .tgz
Bug
thing that needs fixing
cmd:install
related to `npm install`
Priority 2
secondary priority issue
Release 7.x
work is associated with a specific npm 7 release
Release 8.x
work is associated with a specific npm 8 release
#2405
opened Dec 23, 2020 by
mmis1000
[BUG] thing that needs fixing
cmd:install
related to `npm install`
Priority 2
secondary priority issue
Release 7.x
work is associated with a specific npm 7 release
Release 8.x
work is associated with a specific npm 8 release
npm install
started to hang on "still idealTree buildDeps" for 60 seconds if there are dependencies pointing to specific gitlab repository url (a regression compared to npm v6)
Bug
#3359
opened Jun 3, 2021 by
klesun
1 task done
ProTip!
What’s not been updated in a month: updated:<2024-08-23.