Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
why there are yarn.lock and package-lock.json both present?
See original GitHub issueJust wondering why. Since mostly I see it as a mishap. is it?
Also because I am keep getting error after run npm run setup
My versions
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Should I commit yarn.lock and package-lock.json files?
If you commit both the yarn.lock file, AND the package-lock.json files there are a lot of ways that the 2 files can provide...
Read more >Why are yarn.lock and package-lock.json updated after ...
package-lock.json is the lockfile created and managed by npm. It will be created by npm if it doesn't already exist. You should have...
Read more >Yarn lock: how it works and what you risk without ...
When present in the project, yarn.lock is the main source of information about the current versions of dependencies in a project. Yarn uses...
Read more >Package has both yarn.lock and package-lock.json #1516
This package seems to be mixing use of yarn and npm. ... Yarn can import package-lock.json now -- but there are still differences: ......
Read more >yarn.lock
Current package only ... During install, Yarn will only use the top-level yarn.lock file and will ignore any yarn.lock files that exist within...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I just removed yarn.lock. Closing. Thanks guys!
I agree we should centralize around just one of them.