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

doc: add npm add as alias to npm install #160

Merged
merged 1 commit into from
Feb 18, 2019
Merged

doc: add npm add as alias to npm install #160

merged 1 commit into from
Feb 18, 2019

Conversation

ahasall
Copy link
Contributor

@ahasall ahasall commented Feb 14, 2019

No description provided.

@ahasall ahasall requested a review from a team as a code owner February 14, 2019 22:15
@@ -14,7 +14,7 @@ npm-install(1) -- Install a package
npm install <tarball url>
npm install <folder>

alias: npm i
aliases: npm i, npm add
Copy link
Collaborator

Choose a reason for hiding this comment

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

oof, i didn't realize this was an alias. it seems like add should force --save, and it doesn't :-/

Copy link
Contributor Author

@ahasall ahasall Feb 14, 2019

Choose a reason for hiding this comment

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

I've just learnt it. I was trying to do npm adduser but I did npm add user 😀.
Just tried ng add, and it's seems to be forcing --save.

Copy link
Collaborator

Choose a reason for hiding this comment

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

if you have save=false in your .npmrc, does it still force --save?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, if I have save=false in my .npmrc (whether it's local to my project or global), it doesn't force --save.

@zkat zkat added the docs label Feb 18, 2019
@zkat zkat changed the base branch from latest to release-next February 18, 2019 22:31
@zkat zkat merged commit 5d76338 into npm:release-next Feb 18, 2019
@ahasall ahasall deleted the patch-2 branch February 18, 2019 22:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants