npm install fails about ramda HOT 8 CLOSED

I don't have OSX to compare with. I'm having no difficulty on my ancient Win XP box. I have no other working boxes right now to compare. Maybe Mike can see what happens for him in Ubuntu.

Just out of curiosity, is this based on a GitHub pull or an NPM one?

Here are my GitHub log and my NPM one if they offer any clues.

Anyone else using OSX having this issue?

from ramda.

My log was from a fresh github clone of the project.

I see you have a .travis.yml file, but it looks like you haven't run any Travis builds. https://travis-ci.org/CrossEye/ramda/builds

You could try activating Travis builds on the project and see if they succeed. I think they run in Linux.

from ramda.

Ok, I'm seeing something similar in the Travis logs. Trying to figure my way through the dependency chains to determine what's causing the issues, if we still need it, or if we can simply change version.

from ramda.

i set up travis in the Ramda/ramda fork. it is reported "pass" for node 0.10 and "fail" for node 0.8. https://travis-ci.org/Ramda/ramda

the final fatal error is:

npm http 304 https://registry.npmjs.org/rimraf
npm ERR! Error: ENOENT, chmod '/home/travis/build/Ramda/ramda/node_modules/grunt-docco/node_modules/docco/node_modules/highlight.js/lib/languages/go.js'
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! [email protected]
npm ERR! System Linux 2.6.32-042stab079.5
npm ERR! command "/home/travis/.nvm/v0.8.26/bin/node" "/home/travis/.nvm/v0.8.26/bin/npm" "install"
npm ERR! cwd /home/travis/build/Ramda/ramda
npm ERR! node -v v0.8.26
npm ERR! npm -v 1.2.30
npm ERR! path /home/travis/build/Ramda/ramda/node_modules/grunt-docco/node_modules/docco/node_modules/highlight.js/lib/languages/go.js
npm ERR! fstream_path /home/travis/build/Ramda/ramda/node_modules/grunt-docco/node_modules/docco/node_modules/highlight.js/lib/languages/go.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! fstream_finish_call chmod
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack Writer._finish (/home/travis/.nvm/v0.8.26/lib/node_modules/npm/node_modules/fstream/lib/writer.js:305:19)
npm ERR! fstream_stack Object.oncomplete (fs.js:297:15)
npm http 200 https://registry.npmjs.org/ncp
npm http 200 https://registry.npmjs.org/delayed-stream/-/delayed-stream-0.0.5.tgz
npm http 200 https://registry.npmjs.org/jsonfile
npm http GET https://registry.npmjs.org/jsonfile/-/jsonfile-1.1.1.tgz
npm http 200 https://registry.npmjs.org/jsonfile/-/jsonfile-1.1.1.tgz

[email protected] install /home/travis/build/Ramda/ramda/node_modules/grunt-mocha/node_modules/grunt-lib-phantomjs/node_modules/phantomjs
node install.js
Writing location.js file
PhantomJS is already installed at /usr/local/phantomjs/bin/phantomjs.
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/travis/build/Ramda/ramda/npm-debug.log
npm ERR! not ok code 0

One way to fix the build: Simply removing support for node 0.8. lmk if you want me to pull that into the crosseye fork

from ramda.

Definitely worth pulling into CrossEye. I did that and it built properly. But that doesn't address the problem Joe is having in OS X with Node 10.12.

from ramda.

No, that's not the issue:

git clone ramda
cd ramda
npm install

This is what's failing, I'm pretty sure. And this is the error that both Joe and Travis seemed to get:

npm ERR! Error: No compatible version found: minimatch@'^0.3.0'

from ramda.

i ran into the same problem on Mac OS. Not sure why it is working on Ubuntu. anyways, I had to

sudo npm update -g npm

because of some dependencies. Then npm install ran fine.

Not sure how to enforce this for unexpecting users though. This is not just a ramda problem, there's a lot of people complaining about these kinds of errors.

from ramda.

I just ran a brew remove npm && brew install npm and that fixed it. Thanks for the debugging help.

from ramda.