The latest articles on DEV Community by Matt Morgis (@mattmorgis). https://dev.to/mattmorgis https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F37775%2F09610222-b8b8-4d5e-9243-53d6827f086e.jpeg https://dev.to/mattmorgis en Matt Morgis Tue, 02 Apr 2019 15:07:16 +0000 https://dev.to/mattmorgis/what-is-the-history-of-npm-gc https://dev.to/mattmorgis/what-is-the-history-of-npm-gc <p>I didn't get into JavaScript development until about 2016-ish. Therefore, I missed a lot of the early stages of Node.js (and the io.js fork), <code>npm</code>, the rise of all of the frontend frameworks, etc. </p> <p>To my surprise, I learned recently that <code>npm</code>, the package manager that ships by default with Node.js, is actually controlled by a for-profit company and it is not open source. </p> <p>Python's <code>pip</code> and Java's Maven are both open source, and that seems to be the default for other programming language's package managers. </p> <p>There has been a lot of chatter and concern on Twitter about:</p> <ul> <li>moving the registry to the JS Foundation</li> <li>making it decentralized</li> <li>contingency plans should the company sell to a bad actor.</li> </ul> <p>I have some questions I'm hoping someone with context can answer for me:</p> <ul> <li>Was <code>npm</code> always a for-profit company or did it start open source and eventually incorporate?</li> <li>How did Node.js decide to partner and ship with <code>npm</code>?</li> </ul> npm javascript node