> Yarn may well be better than npm, in fact, as far as I can tell it is, but, frankly, npm works well and I'm tired of switching js dependencies, especially rea

> Yarn may well be better than npm, in fact, as far as I can tell it is, but, frankly, npm works well and I'm tired of switching js dependencies, especially really core dependencies like a package manager... Yarn still uses your package.json. I think it will definitely win out over directly using npm since it is better in a couple of ways and, from a user perspective, is just a thin wrapper around the things you're already used to doing. Ways my workflow has changed: npm install . -> yarn npm save --dev pkg -> yarn add --dev pkg npm save pkg -> yarn add pkg npm run command -> yarn run command If you start using it and dislike it, just npm uninstall -g yarn, rm the yarn.lock file and bam, you've still got a normal npm dependency management setup. > If yarn were available for python, I'd switch to it today Project worth keeping your eye on: https://github.com/kennethreitz/pipenv/blob/master/README.rst https://github.com/kennethreitz/pipenv/blob/master/README.rs...