Save time managing and deploying your node.js app

Nodejitsu has joined GoDaddy

We are excited to join GoDaddy to help spearhead their largest Node.js product: Website Builder. Please read our blog post to learn more about customer transition plans and our continued support for Open Source within the node community.

Want to know all the details?
Read the full blog post or read the GoDaddy Announcement.

New Package Manifestations

About the author

nodejitsu nodejitsu

Other popular posts

- Scaling Isomorphic Javascript Code - Keep a node.js server up with Forever - Package.json dependencies done right
- npm cheat sheet - 6 Must Have Node.js Modules

At Nodejitsu we're always looking for a way to make npm better. Our public npm replicas are now serving millions of requests with 99.998% uptime since launching in January. Have you tried it out yet?

npm config set  

But making npm better is more than just about making service more reliable. It's about making everything in your development workflow better. That's why today we're happy to announce the beta of our new package pages! Can't wait to try it out? Sign up today for just $25!

Licenses, Licenses, Licenses

Like so many things around npm determining the correct license for a module is deceptively simple. That is: it is much harder than it seems. Why? Because module authors usually don't include their license in the package.json.

That's why 3rdEden (author of Primus and Lead Front-End Engineer At Nodejitsu) wrote licenses. Now we can bring you all that information in a simple interface:

Not only does it display the list of all licenses for all modules depended on directly, it is also displays the licenses of all modules depended on indirectly. By quickly viewing a list you can be sure what your software license foot print for your application is.

Quickly see what matters

All of the information you need for your packages in a single place.

Readme's rendered as you intended

As module authors we know how important documentation is. We used renderme to ensure that your README files are rendered in the same way as it does on GitHub. No need to change your README files to get them rendered in the way you intended.

As a bonus it also adds line numbers and links to each code snippet so you can easily share them with your team members.

Zero setup time for private modules

If you (or your company) has tried to setup npm-www you know that it can be a bit of a pain to get right on-top of running your own CouchDB server too. You have to setup Redis, and ElasticSearch, getting all the permissions down. The list goes on.

What if you could get all this information for your private modules too? Well you can!

Well. What are you waiting for?!

This is just the first of a lot of new features that have been brewing in our pipeline including:

  • Package notifications: Get an email or first a webhook everytime a module is published
  • Pre-built modules: Get a tarball of your private modules pre-built for your platform of choice including all binary dependencies.
  • ... and More!

So ... what are you waiting for?! Signup today for only $25