Why does a clean yarn install delete modules from yarn.lock?

Asked Sep 15 '21 at 15:40

Active Sep 15 '21 at 15:40

Viewed 1,142 times

In a React Native project: when I delete everything in my node_modules directory, then run yarn v 1.22 against my yarn.lock, modules are deleted from the text of yarn.lock and, consequently, my node_modules install is incomplete.

This is inconvenient when the yarn.lock is committed, then another developer does a pull, tries to run yarn, and gets the results I described.

Is there a way to run yarn so that all files in the module are installed, and nothing is deleted from yarn.lock?

asked Sep 15 '21 at 15:40

johnrubythecat

1,003
1
13
31

Strange... This happens every time? – omeanwell Sep 15 '21 at 15:58
yes. good--it IS strange, right? – johnrubythecat Sep 15 '21 at 18:18
https://mattbatman.com/on-occasion-my-yarn-lockfile-is-the-problem It seems like there are dependencies on package.json! I thought yarn ignored package.json. – johnrubythecat Sep 16 '21 at 01:35
Yarn installs the dependencies in your package.json, thats the purpose of it? – omeanwell Sep 16 '21 at 09:19
I just realized this. Thanks. I thought it had its own files. I'm a little stunned that it requires on a file generated by another tool. – johnrubythecat Sep 20 '21 at 19:04

Why does a clean yarn install delete modules from yarn.lock?

0 Answers0