What you need to know
- Microsoft's GitHub will acquire npm.
- The npm registry is free, and will always be free, according to GitHub's Nat Friedman.
For developers that currently use the registry, the most important takeaway is that it will remain free. npm's blog post states that its registry of packages will remain "public, free, and as available as ever." GitHub's Friedman states that "the public npm registry... will always be available and always be free." Paying customers that use npm Pro, Teams, and Enterprise to host private registries will still be able to do so.
Friedman explains that the focus of this deal is to invest infrastrucutre and platform, improve the core experience, and engage with the community. In the future, GitHub will integrate with npm, allowing developers to trace a change from a GitHub pull request all the way to an npm package version.
When npm was founded, it had a set of goals that its founder says have stayed mostly the same:
- Keep the npm registry running forever (not only for the life of the company).
- Be a company that we can all enjoy working at, and do the best work of our careers up until now.
- Get a big enough exit that I can quit my job and see what comes out of me a second time.
- Share the rewards equitably with the people who got npm to where it is.
The first goal is the most important in relation to this deal. With the GitHub acquisition of npm, the npm team feels comfortable that its registry will be available long after the company is gone. The npm blog post concludes by saying, "This is the end of 'npm, Inc.', the Delaware C Corp. But it's an exciting upgrade for npm."
Sean Endicott brings nearly a decade of experience covering Microsoft and Windows news to Windows Central. He joined our team in 2017 as an app reviewer and now heads up our day-to-day news coverage. If you have a news tip or an app to review, hit him up at email@example.com (opens in new tab).
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.