I have an issue with installing my package siteboot on an i686 system. I get several errors from underlying packages that fail to install (perf-time for example fails with no compatible version found). Everything works fine on 64 bit.
Now, the issue is that if I checkout the repository from github to node_modules/siteboot of my project and then run the bootstrap script that is located in that folder which installs all dependencies manually, I only get that single error from perf-time failing to install and no other errors and I can run my project afterwards even though that error was reported.
Here is the error from perf-time:
npm ERR! Error: No compatible version found: perf-time@'>=1.0.0-0'
npm ERR! Valid install targets:
npm ERR! ["0.1.0"]
npm ERR! at installTargetsError (/usr/local/lib/node_modules/npm/lib/cache.js:719:10)
npm ERR! at next (/usr/local/lib/node_modules/npm/lib/cache.js:698:17)
npm ERR! at /usr/local/lib/node_modules/npm/lib/cache.js:675:5
npm ERR! at saved (/usr/local/lib/node_modules/npm/node_modules/npm-registry-client/lib/get.js:142:7)
npm ERR! at /usr/local/lib/node_modules/npm/node_modules/graceful-fs/polyfills.js:133:7
npm ERR! at Object.oncomplete (fs.js:107:15)
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! firstname.lastname@example.org
npm ERR! System Linux 2.6.32-042stab076.8
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install" "http-server" "path" "JSON" "formidable" "node-fs" "url" "process" "querystring" "crypto" "perf-tim
ers" "walk" "mustache" "csv" "email-templates" "nodemailer" "mysql" "async" "jquery" "multipart" "sys" "posix" "glob" "fs-extra"
npm ERR! cwd /var/www/nodeportal.org/node_modules/siteboot
npm ERR! node -v v0.10.15
npm ERR! npm -v 1.3.5
Is it possible to somehow make npm ignore this error when installing siteboot with "npm install siteboot"? Or is there a solution to perf-time failing to install on my server system?
2.6.32-042stab076.8 #1 SMP Tue May 14 20:38:14 MSK 2013 i686 i686 i386 GNU/Linux
It is not possible to install an invalid package, which is what you're trying to do. One of those (many) packages is trying to install perf-time >= 1.0.0-0, but there is no such version in the npm registry (they only have up to 0.1.0).
I'd suggest narrowing it down to a single install at a time, so you can find which package is failing and then open a bug report on their repo telling them to use a valid version of perf-time instead of one that does not exist.