Whenever I see myself exploring a new language, framework or library, I usually research any relevant information I should know before digging deeper into this new knowledge adventure. Maybe you’re here for the same reason: you’ve been reading lots of tweets from people saying how much they love React, or, likely, you’ve just read an article that stays how React will solve all your problems and other 13 reasons why you should incorporate it in your life, or you’re just tired of the same projects setup with jQuery, and you want to use something new.

One common Javascript flaw I see in repositories I get in touch with is the usage of both yarn.lock and npm-lock.json. This is not on purpose, in most cases is due to the lack of communication on the tooling the repo uses or different points of view on the best tooling for the problem at hand. In this short post, I’m not going to focus on communication strategies for the codebase, nor in which one is better between YARN and NPM.