This article is more than 1 year old
Now GitHub has gulped down NPM Inc, what's next for the JS package registry? Well, some stability will be nice
CTO Ahmad Nassri announces intention to bow out
Jeremy Epling, GitHub's director of product management, made it official just one month after news of the sale agreement broke. According to GitHub CEO Nat Friedman, and confirmed by Epling, the company has three immediate areas of focus.
The first is to "make the investments necessary to ensure that npm is fast, reliable, and scalable". Both GitHub and NPM are heavily used sites. In his farewell post, Nassri revealed that "the npm registry is serving around 125 billion requests at a whopping 6 petabytes per month". He added that the number of packages in the registry has increased from 1 million to 1.3 million since June 2019.
GitHub's own reliability record is not spotless, with significant outages on 27 February and 2 April, for example. On NPM's side, there were a couple of partial outages on 10-11 February. The sites do work well most of the time, though, with NPM reporting 100 per cent uptime in March and April, and 99.13 per cent in February, while GitHub cited 99.91 per cent, 100 per cent and 99.76 per cent (so far) for those three months. Uptime is critical since millions of developers rely on GitHub and/or NPM to do their work.
The way NPM founder Isaac Z Schlueter tells it: "The npm registry is a significant and concrete strategic asset serving GitHub's mission of eliminating transaction costs in software development."
GitHub's other goals for NPM include improving the everyday experience for developers, including work on npm workspaces, which let you manage multiple packages from a single top-level package, and improving security. "Open source security is an important global issue," Friedman noted. ®