build: track package-lock.json for reproducible installs (#838)

Stop gitignoring the lockfile and commit a freshly regenerated one so CI and Docker builds install a pinned dependency tree instead of re-resolving `^` ranges on every run. Fresh resolution matches the versions already building (no version changes). Document the convention in CLAUDE.md. Enables `npm ci` as a follow-up.
This commit is contained in:
Jack Carter
2026-07-09 11:19:59 +02:00
committed by GitHub
parent e7b2214883
commit e8c605047a
3 changed files with 10643 additions and 1 deletions

1
.gitignore vendored
View File

@@ -21,7 +21,6 @@ yarn-error.log*
.idea
package-lock.json
/.next/
/yarn.lock
/generator/openapi/

View File

@@ -8,6 +8,8 @@ Documentation website for [NetBird](https://netbird.io), an open-source WireGuar
There is no test suite in this project. Validate changes with `npm run build`.
`package-lock.json` is committed, so installs are pinned. When you change dependencies in `package.json`, regenerate the lockfile (`npm install`) and commit it in the same change — otherwise local, CI, and Docker builds resolve different trees.
## Common Commands
```bash

10641
package-lock.json generated Normal file

File diff suppressed because it is too large Load Diff