Jul 27, 2017 · 1 min read
I don’t think you should delete it.
If you do, the next time you run yarn it will re-evaluate if there are more recent packages that fulfil your version requirements, and the versions requirements of your transitive dependencies. So chances are it will bump the versions of a bunch of libraries without notifying you.
Don’t get me wrong, bumping dependencies and staying up to date is important. But I rather do that by running yarn upgrade <lib> in a controller manner, than deleting yarn.lock and let everything change at the same time.