Skip to content
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 install foo lacks the implicit @latest that v6 has #2243

Closed
ljharb opened this issue Nov 26, 2020 · 0 comments · Fixed by npm/arborist#211
Closed

[BUG] npm install foo lacks the implicit @latest that v6 has #2243

ljharb opened this issue Nov 26, 2020 · 0 comments · Fixed by npm/arborist#211
Assignees
Labels
Bug thing that needs fixing Priority 1 high priority issue Release 7.x work is associated with a specific npm 7 release

Comments

@ljharb
Copy link
Contributor

ljharb commented Nov 26, 2020

Current Behavior:

I have, say, eslint 7.11.0 installed. I have package-lock=false in .npmrc. I run npm install --save-dev eslint. package.json continues to reference ^7.11.0, and v7.2.0 is what's installed.

Expected Behavior:

package.json should be updated to reference ^7.14.0, and v7.14.0 should be installed, like it does in npm < 7.

Steps To Reproduce:

See above.

Environment:

node: n/a (15)
npm: v7.0.0 - v7.4.1

@ljharb ljharb added Bug thing that needs fixing Needs Triage needs review for next steps Release 7.x work is associated with a specific npm 7 release labels Nov 26, 2020
@wraithgar wraithgar added Priority 2 secondary priority issue Priority 1 high priority issue and removed Needs Triage needs review for next steps Priority 2 secondary priority issue labels Jan 21, 2021
@darcyclarke darcyclarke added this to the OSS - Sprint 23 milestone Jan 25, 2021
@wraithgar wraithgar self-assigned this Jan 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug thing that needs fixing Priority 1 high priority issue Release 7.x work is associated with a specific npm 7 release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants