A journal experiment for the month of May, 2018
I am live-blogging my entire process and thought patterns around work this month. Follow along!
Posts:
- Sun at 12:21 - Sunday morning review
- Fri at 13:23 - mntnr/audit templates
- Fri at 11:47 - npm or yarn?
- Fri at 11:38 - Automatically creating audit templates
- Thu at 15:19 - Goodbye
- Thu at 12:02 - Initial commit for May
All content CC-BY-NC © 2018 Richard Littauer.
I use npm install often when programming. And… I don’t actually know what yarn does. I wonder if I am being inefficient.
I remember hearing that npm5 actually solved a lot of the problems that Yarn was made to address. So, I’ve just googled that, and found this article.
If I’d start a project tomorrow, I would pick npm to manage dependencies, because:
- now it comes with lock file support,
- it does not send package usage information to Facebook (yarn uses Facebook’s npm registry mirror)
Well, that solves that problem. Let’s keep going with npm. I wish there was better content addressing with npm, where it would keep a copy somewhere in my harddrive and then pull from there for versions I already have. I don’t know if someone has done this yet with IPFS, but it sounds like a tool that would make sense. I should ask David Dias or Jeromy.