You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The yarn.lock file should be placed into node_modules.
Or SourceTree or WebStorm will prompt to add it to cvs.
And I metioned a .yarn-integrity file existed in node_modules, and place the yarn.lock into it should be also OK?
The text was updated successfully, but these errors were encountered:
Why not committing yarn.lock file? Basically, this will assure to have a deterministic and reproducable build. I am aware of the bad thing, that yarn.lock also stores URLs, which I would like to see parameterized over any env variable.
However, this is the only way to be totally sure, that the build will run on any machine with the same result.
@cnyyk node_modules is typically gitignored. Project config files, like a lock file, are typically at the root of a repo. yarn.lock should be committed, that's the whole point.
The
yarn.lock
file should be placed into node_modules.Or SourceTree or WebStorm will prompt to add it to cvs.
And I metioned a
.yarn-integrity
file existed in node_modules, and place theyarn.lock
into it should be also OK?The text was updated successfully, but these errors were encountered: