Skip to content
This repository has been archived by the owner on May 2, 2024. It is now read-only.

Don't allow lockfiles #71

Merged
merged 1 commit into from
Jun 29, 2017

Conversation

mastilver
Copy link
Contributor

No description provided.

@sindresorhus
Copy link
Owner

Ugh, yet another dotfile :(

@@ -1,3 +1,6 @@
node_modules<% if (nyc) { %>
.nyc_output
coverage<% } %>
yarn.lock
package-lock.json
npm-shrinkwrap.json
Copy link
Owner

Choose a reason for hiding this comment

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

This one is not generated by default, so I don't see the point in ignoring it.

@@ -1,3 +1,6 @@
node_modules<% if (nyc) { %>
.nyc_output
coverage<% } %>
yarn.lock
package-lock.json
Copy link
Owner

Choose a reason for hiding this comment

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

You're already adding the npmrc file, so this is moot.

@@ -1,3 +1,6 @@
node_modules<% if (nyc) { %>
.nyc_output
coverage<% } %>
yarn.lock
Copy link
Owner

Choose a reason for hiding this comment

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

Not sure I care enough to add this to be honest. I'll think about it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Even if I don't like yarn, I think it should be added so yarn users can contribute without switching tools or manually discard there lockfile

Copy link
Owner

Choose a reason for hiding this comment

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

I like neither yarn nor npm. It's just that I don't use yarn as it's been too unstable for me. I guess you're right though, should be included to prevent it accidentally included in PRs.

@sindresorhus sindresorhus changed the title chore(npm): do not allow lockfiles Don't allow lockfiles Jun 23, 2017
@luftywiranda13
Copy link

@sindresorhus hi Sindre, sorry to bother you here. maybe you wanna answer your reason on sindresorhus/ama#479?

@SamVerschueren
Copy link

SamVerschueren commented Jun 23, 2017

Can't we set the package-lock=false globally and enforce people to do that? I don't really like another dotfile to be honest.

@sindresorhus
Copy link
Owner

Can't we set the package-lock=false globally and enforce people to do that? I don't really like another dotfile to be honest.

We both know that is totally unrealistic…

@sindresorhus sindresorhus merged commit caac7eb into sindresorhus:master Jun 29, 2017
@mastilver mastilver deleted the no-lockfile-for-library branch June 29, 2017 14:52
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants