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

Is there a reason why there is no package-lock.json? #1345

Closed
sunrabbit123 opened this issue Nov 1, 2024 · 1 comment
Closed

Is there a reason why there is no package-lock.json? #1345

sunrabbit123 opened this issue Nov 1, 2024 · 1 comment

Comments

@sunrabbit123
Copy link
Contributor

Question

Typically, developers commit lock files together.

This is not just a practice, but to share detailed versions of information together to prevent bugs caused by simple version differences as much as possible.

Is there a reason?

@samchon
Copy link
Owner

samchon commented Jan 27, 2025

Because this is not a final produc, but a library.

If I commit the package-lock.json version, I cannot rapidly reflect to the minor/patch level updates of devDependencies.

The alternative solution for such case keeping the package-lock.json is configuring every devDependencies to be targetted to the dependabot, but it makes the maintenance difficult due to spam like pouring dependabot's devDependencies' update PRs.

I'd tried that in the past, but it just didn't work. My notification inbox was polluted with dependabot, which caused major problems for my open source development.

@samchon samchon closed this as not planned Won't fix, can't repro, duplicate, stale Jan 27, 2025
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

No branches or pull requests

2 participants