I've tried to install and run node-inspector with a bunch of different commands and still unable to run it:
Jordans-MacBook-Pro:angular-express-blog jordanbaucke$ node-inspector
-bash: node-inspector: command not found
Here is my configuration
Jordans-MacBook-Pro:angular-express-blog jordanbaucke$ node -v
v0.10.15
Jordans-MacBook-Pro:angular-express-blog jordanbaucke$ npm -v
1.3.5
I installed using:
Jordans-MacBook-Pro:angular-express-blog jordanbaucke$ sudo npm install -g node-inspector
Password:
npm http GET https://registry.npmjs.org/node-inspector
npm http 304 https://registry.npmjs.org/node-inspector
npm http GET https://registry.npmjs.org/glob
npm http GET https://registry.npmjs.org/async
npm http GET https://registry.npmjs.org/socket.io
npm http GET https://registry.npmjs.org/express
npm http 304 https://registry.npmjs.org/glob
npm http 304 https://registry.npmjs.org/async
npm http 304 https://registry.npmjs.org/socket.io
npm http 304 https://registry.npmjs.org/express
npm http GET https://registry.npmjs.org/inherits
npm http GET https://registry.npmjs.org/minimatch
npm http GET https://registry.npmjs.org/commander/0.6.1
npm http GET https://registry.npmjs.org/connect/2.7.11
npm http GET https://registry.npmjs.org/range-parser/0.0.4
npm http GET https://registry.npmjs.org/mkdirp/0.3.4
npm http GET https://registry.npmjs.org/cookie/0.1.0
npm http GET https://registry.npmjs.org/buffer-crc32/0.2.1
npm http GET https://registry.npmjs.org/fresh/0.1.0
npm http GET https://registry.npmjs.org/methods/0.0.1
npm http GET https://registry.npmjs.org/cookie-signature/1.0.1
npm http GET https://registry.npmjs.org/send/0.1.0
npm http GET https://registry.npmjs.org/debug
npm http GET https://registry.npmjs.org/base64id/0.1.0
npm http GET https://registry.npmjs.org/policyfile/0.0.4
npm http GET https://registry.npmjs.org/redis/0.7.3
npm http GET https://registry.npmjs.org/socket.io-client/0.9.16
npm http 304 https://registry.npmjs.org/minimatch
npm http 304 https://registry.npmjs.org/inherits
npm http 304 https://registry.npmjs.org/commander/0.6.1
npm http 304 https://registry.npmjs.org/connect/2.7.11
npm http 304 https://registry.npmjs.org/mkdirp/0.3.4
npm http 304 https://registry.npmjs.org/range-parser/0.0.4
npm http 304 https://registry.npmjs.org/cookie/0.1.0
npm http GET https://registry.npmjs.org/lru-cache
npm http GET https://registry.npmjs.org/sigmund
npm http 304 https://registry.npmjs.org/buffer-crc32/0.2.1
npm http 304 https://registry.npmjs.org/fresh/0.1.0
npm http 304 https://registry.npmjs.org/cookie-signature/1.0.1
npm http 304 https://registry.npmjs.org/methods/0.0.1
npm http 304 https://registry.npmjs.org/send/0.1.0
npm http 304 https://registry.npmjs.org/debug
npm http 304 https://registry.npmjs.org/base64id/0.1.0
npm http 304 https://registry.npmjs.org/policyfile/0.0.4
npm http 304 https://registry.npmjs.org/socket.io-client/0.9.16
npm http 304 https://registry.npmjs.org/redis/0.7.3
npm http 304 https://registry.npmjs.org/lru-cache
npm http 304 https://registry.npmjs.org/sigmund
npm http GET https://registry.npmjs.org/mime/1.2.6
npm http GET https://registry.npmjs.org/formidable/1.0.14
npm http GET https://registry.npmjs.org/cookie/0.0.5
npm http GET https://registry.npmjs.org/bytes/0.2.0
npm http GET https://registry.npmjs.org/send/0.1.1
npm http GET https://registry.npmjs.org/pause/0.0.1
npm http GET https://registry.npmjs.org/qs/0.6.5
npm http 304 https://registry.npmjs.org/mime/1.2.6
npm http 304 https://registry.npmjs.org/pause/0.0.1
npm http 304 https://registry.npmjs.org/qs/0.6.5
npm http GET https://registry.npmjs.org/uglify-js/1.2.5
npm http GET https://registry.npmjs.org/active-x-obfuscator/0.0.1
npm http GET https://registry.npmjs.org/xmlhttprequest/1.4.2
npm http GET https://registry.npmjs.org/ws
npm http 304 https://registry.npmjs.org/cookie/0.0.5
npm http 304 https://registry.npmjs.org/formidable/1.0.14
npm http 304 https://registry.npmjs.org/bytes/0.2.0
npm http 304 https://registry.npmjs.org/send/0.1.1
npm http 304 https://registry.npmjs.org/active-x-obfuscator/0.0.1
npm http 304 https://registry.npmjs.org/xmlhttprequest/1.4.2
npm http 304 https://registry.npmjs.org/ws
npm http GET https://registry.npmjs.org/mime
npm http 304 https://registry.npmjs.org/uglify-js/1.2.5
npm http GET https://registry.npmjs.org/zeparser/0.0.5
npm http 304 https://registry.npmjs.org/mime
npm http GET https://registry.npmjs.org/tinycolor
npm http GET https://registry.npmjs.org/options
npm http GET https://registry.npmjs.org/commander
npm http 304 https://registry.npmjs.org/zeparser/0.0.5
npm http 304 https://registry.npmjs.org/commander
npm http 304 https://registry.npmjs.org/options
npm http 304 https://registry.npmjs.org/tinycolor
> ws#0.4.27 install /usr/local/share/npm/lib/node_modules/node-inspector/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)
CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
SOLINK_MODULE(target) Release/bufferutil.node
SOLINK_MODULE(target) Release/bufferutil.node: Finished
CXX(target) Release/obj.target/validation/src/validation.o
SOLINK_MODULE(target) Release/validation.node
SOLINK_MODULE(target) Release/validation.node: Finished
/usr/local/share/npm/bin/node-inspector -> /usr/local/share/npm/lib/node_modules/node-inspector/bin/inspector.js
node-inspector#0.3.2 /usr/local/share/npm/lib/node_modules/node-inspector
├── async#0.2.9
├── glob#3.2.6 (inherits#2.0.0, minimatch#0.2.12)
├── express#3.2.6 (methods#0.0.1, fresh#0.1.0, range-parser#0.0.4, cookie-signature#1.0.1, buffer-crc32#0.2.1, cookie#0.1.0, debug#0.7.2, commander#0.6.1, mkdirp#0.3.4, send#0.1.0, connect#2.7.11)
└── socket.io#0.9.16 (base64id#0.1.0, policyfile#0.0.4, redis#0.7.3, socket.io-client#0.9.16)
Still no change.
Node runs fine, and node --debug app.js works.
I just can't start the inspector.
OS X 10.8.4
This error occurs when the node-inspector is not installed globally.
To install globally use npm install -g node-inspector
If you don't have root permission try the following:
sudo npm install -g node-inspector
Here is the key to your problem:
/usr/local/share/npm/bin/node-inspector -> /usr/local/share/npm/lib/node_modules/node-inspector/bin/inspector.js
Make sure that /usr/local/share/npm/bin is in your PATH environment variable.
Alternatively, you can run node-inspector using the full path
$ /usr/local/share/npm/bin/node-inspector
I ran into this problem on a Windows server. The node-inspector module was installed globally. However, missing from the system path was the directory to globally installed node modules--in my case
C:\Program Files\nodejs\node_modules\npm;
Updating the path (as described in #Prasad's post) resolved my issue running node-debug on a Windows machine.
Please try this-
Open cmd prompt
npm config get prefix
you done this -
C:>npm config get prefix
C:\Users\username\AppData\Roaming\npm
C:>set PATH=%PATH%;C:\Users\yourusername\AppData\Roaming\npm;
Solved !
Related
Why is this build stage in my gitlab pipeline failing with
npm Err! 401: Unable to authenticate, need: Basic realm="Artifactory Realm"
When I run the command $ npm-cli-login -u $USERNAME -p $API_KEY -e $EMAIL -r $REPOSITORY it seems like I get correcly logged in. My correct username gets displayed and the global .npmrc file gets created in my home directory. But when I run npm install or npm i --registry=https://<my_private_repo>.jfrog.io/<my_private_repo> it fails with the 401.
Following output am I seeing in the logs of my failed pipeline stage:
Pulling docker image node:14.15.4 ...
Using docker image sha256:924763541c... for node:14.15.4 with digest node#sha256:cb01e9d98a...
Preparing environment 00:01
Running on runner-ffeacb89-project-...-concurrent-0 via ....r.gitlab.host...
Getting source from Git repository 00:01
Fetching changes with git depth set to 50...
Reinitialized existing Git repository in /builds/gravity/my_test_project/.git/
Checking out 5f7... as dev...
Removing .gradle/
Skipping Git submodules setup
Restoring cache 00:06
Checking cache for my_test_project...
cache.zip is up to date
Successfully extracted cache
Executing "step_script" stage of the job script 01:07
Using docker image sha256:924763541c0c8b3839132... for node:14.15.4 with digest node#sha256:cb01e9d9... ...
$ export GRADLE_USER_HOME=`pwd`/.gradle
$ pwd
/builds/my_test_project
$ cd ~
$ npm install -g npm-cli-login
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator#5.1.5: this library is no longer supported
/usr/local/bin/npm-cli-login -> /usr/local/lib/node_modules/npm-cli-login/bin/npm-cli-login.js
> core-js#3.10.1 postinstall /usr/local/lib/node_modules/npm-cli-login/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"
+ npm-cli-login#0.1.1
added 634 packages from 451 contributors in 34.086s
$ npm-cli-login -u $USERNAME -p $API_KEY -e $EMAIL -r $REPOSITORY
info attempt registry request try #1 at 2:32:54 PM
http request PUT https://<my_private_repo>.jfrog.io/<my_private_repo>/api/npm/npm/-/user/org.couchdb.user:<my_correct_username>
http 201 https://<my_private_repo>.jfrog.io/<my_private_repo>/api/npm/npm/-/user/org.couchdb.user:<my_correct_username>
$ pwd
/root
$ cat .npmrc
//<my_private_repo>.jfrog.io/<my_private_repo>/api/npm/npm//:_authToken=eyJ2...(very long token, looks correct)
$ echo 'always-auth = true' >> .npmrc
$ cat .npmrc
//<my_private_repo>.jfrog.io/<my_private_repo>/api/npm/npm//:_authToken=eyJ2...(very long token, looks correct)
always-auth = true
$ npm i -g #angular/cli
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator#5.1.5: this library is no longer supported
/usr/local/bin/ng -> /usr/local/lib/node_modules/#angular/cli/bin/ng
> #angular/cli#11.2.9 postinstall /usr/local/lib/node_modules/#angular/cli
> node ./bin/postinstall/script.js
+ #angular/cli#11.2.9
added 242 packages from 181 contributors in 12.287s
$ cd /builds/my_test_project/ui
$ printenv NPM_TOKEN
eyJ2Z...(my long token)
$ npm config set //registry.npmjs.org/:_authToken ${NPM_TOKEN}
$ npm install
npm WARN deprecated debug#4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated axios#0.20.0: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated fsevents#2.1.3: "Please update to latest v2.3 or v2.2"
npm WARN deprecated chokidar#2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated har-validator#5.1.5: this library is no longer supported
npm WARN deprecated fsevents#1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm ERR! code E401
npm ERR! Unable to authenticate, need: Basic realm="Artifactory Realm"
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2021-04-16T14_33_25_786Z-debug.log
Cleaning up file based variables 00:00
ERROR: Job failed: exit code 1
This is my build stage in the .gitlab-ci.yml file (Spring Boot Project)
build:
stage: build
image: node:14.15.4
script:
- pwd
- cd ~
- npm install -g npm-cli-login
- npm-cli-login -u $USERNAME -p $API_KEY -e $EMAIL -r $REPOSITORY
- cat .npmrc
- echo 'always-auth = true' >> .npmrc
- cat .npmrc
- npm i -g #angular/cli
- cd /builds/myProjectFolder
- printenv NPM_TOKEN
- npm config set //myrepo.jfrog.io/myrepo/api/npm/npm//:_authToken ${NPM_TOKEN}
- npm install --registry=https://myrepo.jfrog.io/<my_private_repo>/api/npm/npm/
artifacts:
paths:
- app/src/ui/dist/dm-consent-page
expire_in: 5 days
I solved it by using this method: https://gruchalski.com/posts/2020-09-09-authenticate-to-private-jfrog-npm-registry/
After running this curl command I received everything that I needed to put into my global .npmrc file:
curl -u ${JFROG_USER}:${JFROG_ENCRYPTED_PASSWORD} https://${JFROG_ORG}.jfrog.io/${JFROG_ORG}/api/npm/auth
For anyone who's interested, the full script in my gitlab ci pipeline stage now looks like this:
script:
- npm -v
6.14.10
- node -v
v14.15.4
- cd ~
- pwd
/root
# install angular globally
- npm i -g #angular/cli
# create the config file '.npmrc' for authenticating at jFrog when running 'npm install'.
- cat > .npmrc
- echo _auth = ${NPM_AUTH_TOKEN} >> .npmrc <- This is the token that I received after running the curl command from the tutorial / link above
- echo always-auth = true >> .npmrc
- echo email = ${EMAIL} >> .npmrc
# the next line makes npm look for the packages that are annotated with #<my-private-repo> at the JFrog Repo.
- echo #<my-private-repo>:registry=${UI_JFROG_REGESTRY} >> .npmrc
# change back to the project folder.
- cd /builds/<my-project-folder>/ui
# install all packages + the <my-private-repo> package from JFrog.
- npm install
We have a react native app and we configured it with Jenkins for CI/CD .While running the npm install command via Jenkins from the build window (execute shell) its getting failed .
Am using node : v10.16.3 and npm : 6.9.0 with latest jenkins version.
This is the logs for the last run
15:52:30 [cavionnovus-IOS] $ /bin/sh -xe /Users/Shared/Jenkins/tmp/jenkins5253804416691912910.sh
15:52:30 + export PATH=/usr/local/bin
15:52:30 + PATH=/usr/local/bin
15:52:30 + npm install
15:52:34 npm WARN deprecated deep-assign#3.0.0: Check out `lodash.merge` or `merge-options` instead.
15:52:36 npm WARN deprecated core-js#1.2.7: core-js#<2.6.8 is no longer maintained. Please, upgrade to core-js#3 or at least to actual version of core-js#2.
15:52:40 npm WARN deprecated left-pad#1.3.0: use String.prototype.padStart()
15:53:47
15:53:47 > fsevents#1.2.9 install /Users/Shared/Jenkins/Home/workspace/cavionnovus-IOS/node_modules/fsevents
15:53:47 > node install
15:53:47
15:53:47
15:53:47 > grpc#1.23.3 install /Users/Shared/Jenkins/Home/workspace/cavionnovus-IOS/node_modules/grpc
15:53:47 > node-pre-gyp install --fallback-to-build --library=static_library
15:53:47
15:53:48 npm WARN react-navigation-stack#1.9.4 requires a peer of react-native-screens#^1.0.0 || ^1.0.0-alpha but none is installed. You must install peer dependencies yourself.
15:53:48 npm WARN react-navigation-drawer#2.2.2 requires a peer of react-native-screens#^1.0.0 || ^1.0.0-alpha but none is installed. You must install peer dependencies yourself.
15:53:48 npm WARN eslint-plugin-react#7.12.4 requires a peer of eslint#^3.0.0 || ^4.0.0 || ^5.0.0 but none is installed. You must install peer dependencies yourself.
15:53:48 npm WARN eslint-plugin-react-native#3.6.0 requires a peer of eslint#^3.17.0 || ^4 || ^5 but none is installed. You must install peer dependencies yourself.
15:53:48 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.9 (node_modules/fsevents):
15:53:48 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.9 install: `node install`
15:53:48 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: spawn sh ENOENT
15:53:48
15:53:48 npm ERR! file sh
15:53:48 npm ERR! path sh
15:53:48 npm ERR! code ELIFECYCLE
15:53:48 npm ERR! errno ENOENT
15:53:48 npm ERR! syscall spawn sh
15:53:48 npm ERR! grpc#1.23.3 install: `node-pre-gyp install --fallback-to-build --library=static_library`
15:53:48 npm ERR! spawn sh ENOENT
15:53:48 npm ERR!
15:53:48 npm ERR! Failed at the grpc#1.23.3 install script.
15:53:48 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
There wont be any issues while running the same on windows machine , the isssue not there while running the npm commands from the jenkins workspace manualy .
So from the logs i think jenkins blocking creating new process from the build .
while running the command manually we could see that the dependency grpc is downloaded via remotely . that may be a new process and jenkin blocks / kill that child process.
This is the command i used on the build window of Jenkin
export PATH=/usr/local/bin
$sudo npm install
please help me to get ride of this issue .
I have an app that uses the Rails framework and implements AngularJs as part of the front end.
I have pushed everything to Heroku and have the Heroku Toolbelt installed, but when I try to migrate the db using "heroku run rake db:migrate" I receive the following error(s):
Installing core plugins heroku-cli-addons, heroku-apps, heroku-fork, heroku-git, heroku-local, heroku-run, heroku-status...
Error installing package. Try running again with GODE_DEBUG=info to see more output.
! `run` is not a heroku command.
! Perhaps you meant `-h`, `2fa`, `auth`, `join`, `open`, `orgs`, `pg`, `ps` or `rake`.
! See `heroku help` for a list of available commands.
I then run the command "GODE_DEBUG=info heroku run rake db:migrate" and receive this error:
npm ERR! Darwin 14.5.0
npm ERR! argv "/Users/Christopher_Pelnar/.heroku/node-v4.2.1-darwin-x64/bin/node" "/Users/Christopher_Pelnar/.heroku/node-v4.2.1-darwin-x64/lib/node_modules/npm/cli.js" "install" "heroku-cli-addons" "heroku-apps" "heroku-fork" "heroku-git" "heroku-local" "heroku-run" "heroku-status" "--loglevel=info"
npm ERR! node v4.2.1
npm ERR! npm v3.3.8
npm ERR! code ECONNRESET
npm ERR! network tunneling socket could not be established, cause=connect ETIMEDOUT 198.105.254.228:8080
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Please include the following file with any support request:
npm ERR! /Users/Christopher_Pelnar/.heroku/npm-debug.log
Removing the proxy settings resolved the issue:
npm config rm proxy
npm config rm https-proxy
npm config set registry=http://registry.npmjs.org/
npm config set strict-ssl false
It's worked for me!
Hello I try to execute nodejs job in jenkins:
Jenkins integration with Grunt
But I can't connect to registry.npmjs.org/ throw Jenkins.
I set the Proxy in Jenkins in Plugins->Advanced but I get stil this error:
Started by user anonymous
Building in workspace /var/lib/jenkins/jobs/TempDemo/workspace
$ /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/recent_node_0.11.11_/bin/npm install -g grunt-cli#~0.1.0
npm http GET https://registry.npmjs.org/grunt-cli
npm http GET https://registry.npmjs.org/grunt-cli
npm http GET https://registry.npmjs.org/grunt-cli
npm ERR! Error: connect ECONNREFUSED
npm ERR! at exports._errnoException (util.js:682:11)
npm ERR! at Object.afterConnect [as oncomplete] (net.js:947:19)
npm ERR! { [Error: connect ECONNREFUSED]
npm ERR! stack: 'Error: connect ECONNREFUSED\n at exports._errnoException (util.js:682:11)\n at Object.afterConnect [as oncomplete] (net.js:947:19)',
npm ERR! code: 'ECONNREFUSED',
npm ERR! errno: 'ECONNREFUSED',
npm ERR! syscall: 'connect' }
npm ERR!
npm ERR! If you are behind a proxy, please make sure that the
npm ERR! 'proxy' config is set properly. See: 'npm help config'
What should I do now?
I only have a stopgap solution to this as I couldn't find any information on configuring the plugin to work with a proxy. I created a wrapper around the npm executable which sets the proxy details before calling the underlying npm script. The steps:
Setup the NodeJS Installation, start a job which uses it and get the failure (as above). This should leave a Node installation folder in /tools. I see for you this is "/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/recent_node_0.11.11_".
Navigate to the /bin folder at this location.
Rename the npm executable link: "mv npm npm-actual"
Create a new npm file: touch npm
Set the contents as follows:
\#!/bin/sh
/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/recent_node_0.11.11_/bin/npm-actual config set proxy "<proxy url with optional credentials>"
/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/recent_node_0.11.11_/bin/npm-actual config set https-proxy "<proxy url with optional credentials>"
/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/recent_node_0.11.11_/bin/npm-actual "$#"
Be sure that this new npm script is owned by the Jenkins user and that it is marked executable.
Re-run the Jenkins job, it should this time make use of the proxy settings above and be able to download what it needs. These settings mimic those found in ~/.npmrc and more info can be found here:
http://jjasonclark.com/how-to-setup-node-behind-web-proxy
Hope that helps. If anyone has a better, more correct solution I'd love to hear it as well.
You can set NPM to use a proxy, you may need to sudo
npm config set proxy http://yourproxy.com:80
I'm getting a error when trying to run the web version. (everything works fine one the phone).
Here is the error I get from the console.
[INFO] JavaScript check complete
[INFO] Verifying your configuration settings...
[INFO] Configuration settings check complete
[INFO] Development build created. Use forge run to run your app.
[INFO] Forge tools running at version 3.3.71
[ERROR] Failed when running npm: npm WARN package.json forge-web#0.0.1 No description
npm WARN package.json forge-web#0.0.1 No repository field.
npm WARN package.json forge-web#0.0.1 No README data
npm http GET https://registry.npmjs.org/express
npm http 304 https://registry.npmjs.org/express
npm WARN engine express#3.4.6: wanted: {"node":">= 0.8.0"} (current: {"node":"v0.6.12","npm":"1.3.12"})
npm http GET https://registry.npmjs.org/connect/2.11.2
npm http GET https://registry.npmjs.org/commander/1.3.2
npm http GET https://registry.npmjs.org/range-parser/0.0.4
npm http GET https://registry.npmjs.org/mkdirp/0.3.5
npm http GET https://registry.npmjs.org/cookie/0.1.0
npm http GET https://registry.npmjs.org/buffer-crc32/0.2.1
npm http GET https://registry.npmjs.org/fresh/0.2.0
npm http GET https://registry.npmjs.org/methods/0.1.0
npm http GET https://registry.npmjs.org/send/0.1.4
npm http GET https://registry.npmjs.org/cookie-signature/1.0.1
npm http GET https://registry.npmjs.org/debug
npm http 304 https://registry.npmjs.org/commander/1.3.2
npm http 304 https://registry.npmjs.org/range-parser/0.0.4
npm http 304 https://registry.npmjs.org/connect/2.11.2
npm http 304 https://registry.npmjs.org/mkdirp/0.3.5
npm http 304 https://registry.npmjs.org/cookie/0.1.0
npm http 304 https://registry.npmjs.org/methods/0.1.0
npm http 304 https://registry.npmjs.org/fresh/0.2.0
npm http 304 https://registry.npmjs.org/buffer-crc32/0.2.1
npm http 304 https://registry.npmjs.org/debug
npm http 304 https://registry.npmjs.org/send/0.1.4
npm http 304 https://registry.npmjs.org/cookie-signature/1.0.1
npm WARN engine connect#2.11.2: wanted: {"node":">= 0.8.0"} (current: {"node":"v0.6.12","npm":"1.3.12"})
npm http GET https://registry.npmjs.org/keypress
npm http GET https://registry.npmjs.org/mime
npm http GET https://registry.npmjs.org/raw-body/1.1.2
npm http GET https://registry.npmjs.org/qs/0.6.5
npm http GET https://registry.npmjs.org/bytes/0.2.1
npm http GET https://registry.npmjs.org/negotiator/0.3.0
npm http GET https://registry.npmjs.org/multiparty/2.2.0
npm http GET https://registry.npmjs.org/uid2/0.0.3
npm http GET https://registry.npmjs.org/pause/0.0.1
npm http 304 https://registry.npmjs.org/keypress
npm http 200 https://registry.npmjs.org/mime
npm http 200 https://registry.npmjs.org/negotiator/0.3.0
npm http GET https://registry.npmjs.org/negotiator/-/negotiator-0.3.0.tgz
npm http 200 https://registry.npmjs.org/raw-body/1.1.2
npm http 304 https://registry.npmjs.org/bytes/0.2.1
npm http GET https://registry.npmjs.org/raw-body/-/raw-body-1.1.2.tgz
npm http 304 https://registry.npmjs.org/uid2/0.0.3
npm http 304 https://registry.npmjs.org/pause/0.0.1
npm http 200 https://registry.npmjs.org/multiparty/2.2.0
npm http GET https://registry.npmjs.org/multiparty/-/multiparty-2.2.0.tgz
npm http 200 https://registry.npmjs.org/qs/0.6.5
npm http GET https://registry.npmjs.org/qs/-/qs-0.6.5.tgz
npm http 200 https://registry.npmjs.org/negotiator/-/negotiator-0.3.0.tgz
npm http 200 https://registry.npmjs.org/raw-body/-/raw-body-1.1.2.tgz
npm ERR! addPlacedTarball Could not remove "/home/eugene/.npm/negotiator/0.3.0/package"
npm ERR! error rolling back Error: UNKNOWN, unknown error '/home/eugene/Vouch/trigger/development/web/node_modules/express/node_modules/connect'
npm ERR! error rolling back connect#2.11.2 { [Error: UNKNOWN, unknown error '/home/eugene/Vouch/trigger/development/web/node_modules/express/node_modules/connect']
npm ERR! error rolling back errno: -1,
npm ERR! error rolling back code: 'UNKNOWN',
npm ERR! error rolling back path: '/home/eugene/Vouch/trigger/development/web/node_modules/express/node_modules/connect' }
npm ERR! error rolling back Error: UNKNOWN, unknown error '/home/eugene/Vouch/trigger/development/web/node_modules/express'
npm ERR! error rolling back express#3.4.6 { [Error: UNKNOWN, unknown error '/home/eugene/Vouch/trigger/development/web/node_modules/express']
npm ERR! error rolling back errno: -1,
npm ERR! error rolling back code: 'UNKNOWN',
npm ERR! error rolling back path: '/home/eugene/Vouch/trigger/development/web/node_modules/express' }
npm ERR! Error: UNKNOWN, unknown error '/home/eugene/.npm/negotiator/0.3.0/package'
npm ERR! If you need help, you may report this log at:
npm ERR! <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR! <npm-#googlegroups.com>
npm ERR! System Linux 3.2.0-41-generic
npm ERR! command "node" "/usr/local/bin/npm" "install"
npm ERR! cwd /home/eugene/Vouch/trigger/development/web
npm ERR! node -v v0.6.12
npm ERR! npm -v 1.3.12
npm ERR! path /home/eugene/.npm/negotiator/0.3.0/package
npm ERR! code UNKNOWN
npm ERR! errno -1
npm http 200 https://registry.npmjs.org/qs/-/qs-0.6.5.tgz
npm ERR! addPlacedTarball Could not remove "/home/eugene/.npm/qs/0.6.5/package"
npm http 200 https://registry.npmjs.org/multiparty/-/multiparty-2.2.0.tgz
npm ERR! addPlacedTarball Could not remove "/home/eugene/.npm/multiparty/2.2.0/package"
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/eugene/Vouch/trigger/development/web/npm-debug.log
npm ERR! not ok code undefined
npm ERR! not ok code -1
The problem is that the version of express used in Trigger Web apps needs a newer version of node (at least 0.8) than the version in the official Ubuntu LTS repositories (0.6).
You can install node 0.10 from a PPA, which should solve your problem: https://launchpad.net/~chris-lea/+archive/node.js/