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

Ignore package-lock.json #476

Merged
merged 1 commit into from
Apr 9, 2018
Merged

Ignore package-lock.json #476

merged 1 commit into from
Apr 9, 2018

Conversation

gabegorelick
Copy link
Contributor

PapaParse should either commit package-lock.json, or explicitly ignore it. npm still has some bugs that cause a lot of package-lock.json churn, which will be compounded by PapaParse's support for older Node (and npm) versions. So let's go with ignore for now.

jQuery made a similar decision: jquery/jquery@7037fac

PapaParse should either commit package-lock.json, or explicitly
ignore it. npm still has some bugs that cause a lot of package-lock.json
churn, which will be compounded by PapaParse's support for older
Node (and npm) versions. So let's go with ignore for now.
@pokoli pokoli merged commit 802ab31 into mholt:master Apr 9, 2018
@pokoli
Copy link
Collaborator

pokoli commented Apr 9, 2018

Thanks for your contribution!

@gabegorelick gabegorelick deleted the package-lock branch April 9, 2018 20:05
gabegorelick added a commit to gabegorelick/PapaParse that referenced this pull request Apr 9, 2018
This is similar to mholt#476. It allows devs to use yarn to manage
their dependencies if they want.
@gabegorelick gabegorelick mentioned this pull request Apr 9, 2018
pokoli pushed a commit that referenced this pull request Apr 10, 2018
Similar to #476. It allows developers to use yarn to manage their dependencies if they want.
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.

2 participants