https://github.com/boneskull/pkg-lock-churn
https://github.com/npm/cli/issues/6301
https://github.com/boneskull/pkg-lock-churn
Last synced: 24 days ago
JSON representation
https://github.com/npm/cli/issues/6301
- Host: GitHub
- URL: https://github.com/boneskull/pkg-lock-churn
- Owner: boneskull
- Created: 2024-01-04T21:27:18.000Z (about 2 years ago)
- Default Branch: main
- Last Pushed: 2024-01-04T21:27:30.000Z (about 2 years ago)
- Last Synced: 2025-04-04T06:12:57.991Z (10 months ago)
- Size: 25.4 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# example of package-lock.json churn
This reproduces the issue in https://github.com/npm/cli/issues/6301
## Steps to reproduce
1. Use Node.js v20.10.0
2. Use npm v10.2.3
3. Clone this repo
4. Checkout the `conflict` branch
5. Rebase the `conflict` branch onto `main`.
6. Resolve the conflict in `packages/something/package.json` by combining the changes.
7. Run `npm install` to update `package-lock.json`.
8. Run `git diff` to see the churn in `package-lock.json`.
## Red Herrings Abound!
- I don't know if the workspace is necessary.
- I don't know if conflict resolution is necessary.
## Not a Red Herring
I can only seem to make this happen with `devDependencies`.