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] Bad error wording consequent to typo #3670

Closed
1 task done
Aster89 opened this issue Aug 20, 2021 · 1 comment · Fixed by #4573
Closed
1 task done

[BUG] Bad error wording consequent to typo #3670

Aster89 opened this issue Aug 20, 2021 · 1 comment · Fixed by #4573
Labels
Bug thing that needs fixing Priority 2 secondary priority issue Release 7.x work is associated with a specific npm 7 release

Comments

@Aster89
Copy link

Aster89 commented Aug 20, 2021

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

When I entered

$ npm isntall --save-dev kss

I got

npm ERR! The `npm ci` command can only install with an existing package-lock.json or
npm ERR! npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or
npm ERR! later to generate a package-lock.json file, then try again.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/enrico/.npm/_logs/2021-08-20T15_54_49_990Z-debug.log

and so I spent quite a lot surfing the web for a solution... except that there's no problem to solve, as I have simply written isntall instead of install.

Expected Behavior

A better wording such as this:

$ npm isntall --save-dev kss
npm ERR! The `isntall` command does not exist. Do you mean `install`?

Steps To Reproduce

See above

Environment

  • OS: archlinux
  • Node:
  • npm: 7.21.0
@Aster89 Aster89 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 Aug 20, 2021
@ljharb
Copy link
Collaborator

ljharb commented Aug 20, 2021

I'd expect isntall to be an alias for install, not ci.

@wraithgar wraithgar added Priority 2 secondary priority issue and removed Needs Triage needs review for next steps labels Mar 16, 2022
@nlf nlf closed this as completed in #4573 Mar 17, 2022
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 2 secondary 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