If you missed our initial announcement, look no further! A few weeks ago we announced our new packages page that was available for any of our private npm customers. Last week we released most of that code as Open Source as part of browsenpm.org, our new interface for visualizing
npm packages and metadata.
We were able to do this thanks to the resuable components offered by bigpipe, written by Nodejitsu's own Arnout Kazemier. So what are you waiting for? Go check it out on the web or on GitHub!
Don't we already have a packages page?
The npmjs.org website has been around a long time. While it has gotten us this far, its age was starting to show. It had grown to a place where it was actually easier to reimagine it as a new project instead of changing the legacy implementation. Plus, on top of that, we were able to able to implement a bunch of awesome features:
- Easily view your dependency license footprint
- Quickly view the most recent package information
- Cleanly rendered readmes
- And more to come!
And dependencies too!
Combined with the
npm-dependencies-pagelet we give you a better
picture of what a module contains and what you depend on. Whether you are a module author or module user, we have found this information to be invaluable to visualize in a simple manner.
Global registry status information
The npm registry itself has grown beyond just a single organization. There almost half a dozen production replicas running right now! To show the depth of this information we wanted the homepage of browsenpm.org to show a map of all the replica registries you have to choose from when installing your npm packages.
We try and give an accurate metric on how up to date, how fast and how these metrics change over time. We believe this will help all of you choose the right replica depending on your area of the world. We want to make it transparent to see how well
npm is distributed.
Whats next and what does this mean for you?
The browsenpm.org site is a production application written using
bigpipe which allows us to easily reuse front end componenets called pagelets. If you would like to learn more about
bigpipe, checkout @3rdEden's slides or the recording from EmpireJS.
What we hope to provide with browsenpm.org is deeper insight and transparency into the npm packages you know and love. We want an interface that enables developers to understand more about their software and how interlinked it all is. With the growth of
npm and the module ecosystem this information will only get more important as we evolve as a community.