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.

Sign up for GitHub

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

Jump to bottom

chore: ignore package-lock.json #55

Closed
wants to merge 1 commit into from
Closed

chore: ignore package-lock.json #55

wants to merge 1 commit into from

Conversation

curbengh
Copy link
Contributor

No description provided.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 2f825b7 on weyusi:package-lock into a4fb0d8 on hexojs:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 2f825b7 on weyusi:package-lock into a4fb0d8 on hexojs:master.

@yoshinorin
Copy link
Member

yoshinorin commented Jul 1, 2019 •
edited
Loading

@weyusi
Last year we discussed package-lock.json & yarn.lock.
As discussed in hexo 3370, currently not clear which use. So, I can't judge this PR.

@curbengh
Copy link
Contributor Author

curbengh commented Jul 1, 2019

Consensus seem to lean on having package-lock.

@curbengh curbengh closed this Jul 1, 2019
@curbengh curbengh deleted the package-lock branch July 1, 2019 03:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@curbengh @coveralls @yoshinorin @weyusi