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

Suggestion: Remove package-lock.json from .gitignore files #615

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

chreke
Copy link

@chreke chreke commented Apr 27, 2022

Hello and thanks for the great work on MAL! I've just started working through it and am really enjoying it so far. Something I found odd however is that package-lock.json appears in a few .gitignore files. Was this intentional?

AFAIK package-lock.json file is intended to be checked in to source control in order to make builds reproducible; without a package-lock.json file npm install becomes non-deterministic.

See e.g. https://docs.npmjs.com/cli/v8/configuring-npm/package-lock-json:

package-lock.json is automatically generated for any operations where
npm modifies either the node_modules tree, or package.json. It describes
the exact tree that was generated, such that subsequent installs are
able to generate identical trees, regardless of intermediate dependency
updates.

This file is intended to be committed into source repositories, and
serves various purposes: [...]

As such, this PR removes package-lock.json from the .gitignore files in root and impls

The package-lock.json file is intended to be checked in to source
control in order to make builds reproducible; without
a package-lock.json file `npm install` becomes non-deterministic.

See e.g.
https://docs.npmjs.com/cli/v8/configuring-npm/package-lock-json:

> package-lock.json is automatically generated for any operations where
> npm modifies either the node_modules tree, or package.json. It describes
> the exact tree that was generated, such that subsequent installs are
> able to generate identical trees, regardless of intermediate dependency
> updates.
>
> This file is intended to be committed into source repositories, and
> serves various purposes:
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.

None yet

1 participant