Skip to content

Commit

Permalink
chore: do not create package-lock.json
Browse files Browse the repository at this point in the history
  • Loading branch information
@epoberezkin
epoberezkin committed Mar 25, 2018
1 parent 309f9e3 commit 60f31ae
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions .npmrc
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
package-lock=false

2 comments on commit 60f31ae

@moander
Copy link

@moander moander commented on 60f31ae Mar 2, 2021

Choose a reason for hiding this comment

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

Why is package-lock disabled?

@epoberezkin
Copy link
Member Author

@epoberezkin epoberezkin commented on 60f31ae Mar 2, 2021 •
edited
Loading

Choose a reason for hiding this comment

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

because it is locking versions in downstream dependencies, that can create additional version conflicts or redundancy. The common practice seems to be to use lock file in the applications, and not to use it in the libraries.

Please sign in to comment.