Am 24.06.12 17:04, schrieb Phil Dobbin: > Hi, all. > > I've just ran `sudo port selfupdate` which told me there was a new > version of npm. So I upgraded: > > `sudo port upgrade outdated > ---> Computing dependencies for npm > ---> Fetching archive for npm > ---> Attempting to fetch npm-1.1.32_0.darwin_10.noarch.tbz2 from > http://packages.macports.org/npm > ---> Attempting to fetch npm-1.1.32_0.darwin_10.noarch.tbz2.rmd160 from > http://packages.macports.org/npm > ---> Installing npm @1.1.32_0 > ---> Cleaning npm > ---> Computing dependencies for npm > ---> Deactivating npm @1.1.24_0 > ---> Cleaning npm > ---> Activating npm @1.1.32_0` > > & now I'm getting: > > `$ npm -h > bash: npm: command not found` > > I did a readlink on /opt/local/bin/npm: > > `$ readlink npm > /opt/local/var/macports/build/_Volumes_work_mports_dports_devel_npm/npm/work/destroot/opt/local/lib/node_modules/npm/bin/npm-cli.js` > > & something to my untrained eye looks amiss. > > Any help appreciated. > > Cheers, > > Phil... > This is a bug. I'm working on it.
-- Christoph _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
