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

Added a npmrc to avoid generating lock files #194

Merged
merged 1 commit into from
Mar 18, 2018
Merged

Conversation

sunesimonsen
Copy link
Member

No description provided.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 93.663% when pulling abc5366 on ssimonsen/npmrc into 9475168 on master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 93.663% when pulling abc5366 on ssimonsen/npmrc into 9475168 on master.

Copy link
Member

@papandreou papandreou left a comment

Choose a reason for hiding this comment

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

Not sure exactly what save-prefix='' is good for, but I trust you :)

@sunesimonsen
Copy link
Member Author

sunesimonsen commented Mar 18, 2018

Not sure exactly what save-prefix='' is good for, but I trust you :)

We have that in unexpected. It is to use exact versions when using npm install --save foobar.

@sunesimonsen sunesimonsen merged commit 56e4557 into master Mar 18, 2018
@sunesimonsen sunesimonsen deleted the ssimonsen/npmrc branch March 18, 2018 19:49
@papandreou
Copy link
Member

It is to use exact versions when using npm install --save foobar.

I thought that would be save-exact=false?

@papandreou
Copy link
Member

Ah, when in doubt, look it up: https://docs.npmjs.com/misc/config#save-prefix

It seems to be a generalization of the boolean save-exact option.

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.

3 participants