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

tools: remove stray package-lock.json file #14873

Closed
wants to merge 2 commits into from
Closed

Conversation

Trott
Copy link
Member

@Trott Trott commented Aug 16, 2017

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

Before the ESLint updates were automated, a stray package-lock.json file
was accidentally introduced in the tools directory. This change removes
it.
@nodejs-github-bot nodejs-github-bot added the tools Issues and PRs related to the tools directory. label Aug 16, 2017
@Trott
Copy link
Member Author

Trott commented Aug 16, 2017

@refack
Copy link
Contributor

refack commented Aug 16, 2017

Way is it stray?

Copy link
Contributor

@cjihrig cjihrig left a 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?

Copy link
Contributor

@refack refack left a 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?

@refack
Copy link
Contributor

refack commented Aug 17, 2017

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 module_modules validity "checksum".

@not-an-aardvark
Copy link
Contributor

@refack I think the lockfile is redundant as a checksum, given that we already check the dependencies into source control.

@refack
Copy link
Contributor

refack commented Aug 17, 2017

Personally I'd rather check in the metadata (i.e. package.json and package-lock.json) and not the actual dependencies, but that a different issue.
So LGTM it current context.

@refack
Copy link
Contributor

refack commented Aug 17, 2017

@Trott added a commit with --no-package-lock in update-eslint.sh so it won't be created when updating (possibly also avoiding some git shenanigans when moving back and forth between branches).

@Trott
Copy link
Member Author

Trott commented Aug 18, 2017

jasnell pushed a commit that referenced this pull request Aug 18, 2017
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]>
@jasnell
Copy link
Member

jasnell commented Aug 18, 2017

Landed in b5bad25

@jasnell jasnell closed this Aug 18, 2017
MylesBorins pushed a commit that referenced this pull request Sep 10, 2017
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]>
@MylesBorins MylesBorins mentioned this pull request Sep 10, 2017
MylesBorins pushed a commit that referenced this pull request Sep 12, 2017
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]>
@MylesBorins
Copy link
Contributor

Doesn't look like the stray lock made it to v6.x

@Trott Trott deleted the stray-lock branch January 13, 2022 22:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tools Issues and PRs related to the tools directory.
Projects
None yet
Development

Successfully merging this pull request may close these issues.