npm 1.0: Released

npm 1.0 has been released. Here are the highlights:

  • Global vs local installation
  • ls displays a tree, instead of being a remote search
  • No more “activation” concept – dependencies are nested
  • Updates to link command
  • Install script cleans up any 0.x cruft it finds. (That is, it removes old packages, so that they can be installed properly.)
  • Simplified “search” command. One line per package, rather than one line per version.
  • Renovated “completion” approach
  • More help topics
  • Simplified folder structure

The focus is on npm being a development tool, rather than an apt-wannabe.

Installing it

To get the new version, run this command:

curl | sh 

This will prompt to ask you if it’s ok to remove all the old 0.x cruft. If you want to not be asked, then do this:

curl | clean=yes sh 

Or, if you want to not do the cleanup, and leave the old stuff behind, then do this:

curl | clean=no sh 

A lot of people in the node community were brave testers and helped make this release a lot better (and swifter) than it would have otherwise been. Thanks 🙂

Code Freeze

npm will not have any major feature enhancements or architectural changes for at least 6 months. There are interesting developments planned that leverage npm in some ways, but it’s time to let the client itself settle. Also, I want to focus attention on some other problems for a little while.

Of course, bug reports are always welcome.

See you at NodeConf!

This entry was posted in npm. Bookmark the permalink.

8 Responses to npm 1.0: Released

  1. I was worried that this would require lots of work to re-plumb htracr.

    In the end, I just had to add “sudo” and “-g” to the instructions.

    Thanks! 🙂

  2. Pingback: Events: Team Node.js in the City of Roses « Joyeur

  3. Pingback: Node Roundup: npm 1.0, brain, nTunes, everyauth

  4. Pingback: NodeConf 2011 « Ted Leung on the Air

  5. Pingback: Elegant Code » Taking Baby Steps with Node.js – npm 1.0

  6. To install things that I wanted command line access to like jake or expresso:
    I used sudo install -g {package}

    Awesome stuff Isaac!

  7. Hi Jamund.

    I had to do this to make it work, because my old NPM was installed as root initially:

    sudo -s
    curl | clean=yes sh
    npm install

    That seemed to do the trick!

    • WangZhen says:

      I can’t find libssl-dev package in fedora.
      The installation was failed when I use openlibssl-devel instead of libssl-dev.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s