-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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
tools: remove stray package-lock.json file #14873
Conversation
Before the ESLint updates were automated, a stray package-lock.json file was accidentally introduced in the tools directory. This change removes it.
Way is it stray? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Should we .gitignore
it too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is it stray?
It was my comment #13895 (comment) that lead to it's inclusion. I still think it's ok to have it here as a sort of a |
@refack I think the lockfile is redundant as a checksum, given that we already check the dependencies into source control. |
Personally I'd rather check in the metadata (i.e. |
@Trott added a commit with |
CI with @refack's addition: https://ci.nodejs.org/job/node-test-pull-request/9742/ |
Before the ESLint updates were automated, a stray package-lock.json file was accidentally introduced in the tools directory. This change removes it. PR-URL: #14873 Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Alexey Orlenko <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Timothy Gu <[email protected]> Reviewed-By: Refael Ackermann <[email protected]>
Landed in b5bad25 |
Before the ESLint updates were automated, a stray package-lock.json file was accidentally introduced in the tools directory. This change removes it. PR-URL: #14873 Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Alexey Orlenko <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Timothy Gu <[email protected]> Reviewed-By: Refael Ackermann <[email protected]>
Before the ESLint updates were automated, a stray package-lock.json file was accidentally introduced in the tools directory. This change removes it. PR-URL: #14873 Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Alexey Orlenko <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Timothy Gu <[email protected]> Reviewed-By: Refael Ackermann <[email protected]>
Doesn't look like the stray lock made it to v6.x |
Before the ESLint updates were automated, a stray package-lock.json file
was accidentally introduced in the tools directory. This change removes
it.
Checklist
Affected core subsystem(s)
tools