npm install fails on 1.0.4 about opencollective-cli

[prabhu]

Please take your time for the new fix. Even Q4 2018 is actually very good.

[asood123]

Sorry about that. We are working on fixing it right now.

[asood123]

We unpublished the offending version to unblock everyone. Working on new version to get the original fix out.

[prabhu]

I think your package is the new leftPad now. Our whole team is now stuck because one of the package we use has ^1.0.3 for opencollective.

[amatiasq]

NPM is on fire!!! 💩

[tsuna]

I'm also still regularly running into this issue

npm ERR! path /code/web/node_modules/opencollective/dist/bin/opencollective.js
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod '/code/web/node_modules/opencollective/dist/bin/opencollective.js'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent 

[kurtinatlanta]

i'd prefer to not have this dependency at all and not have it run some postinstall script that breaks our builds.

i support what people are trying to do, but, ideally, you'd find a better way to achieve your goal.

if a transitive dependency to this project continues to cause us issues, we'll have to either avoid opencollective projects entirely, ask the owners to remove it (which one has already graciously done), or fork the repos and 'fix' them not to depend on opencollective.

[xdamman]

Sorry about those issues, we didn't realize there would be so many edge cases (node version 4x on multiple OS/environments, etc.).

We just published a very lightweight version that doesn't have any dependency: https://github.com/opencollective/opencollective-postinstall

Just replace in your package.json the opencollective dependency with opencollective-postinstall and in scripts.postinstall section, replace opencollective postinstall with opencollective-postinstall

Let us know your thoughts and pull requests welcome!

[irrg]

@xdamman worked out in my scenario and I've done pull requests for both the nuxt 1.4 branch and the current dev branch. FWIW, you might want to close the existing issues that came along with from the opencollective-cli repo 😜

[kurtinatlanta]

We get this error on our build box with (I believe 1.03):

> [email protected] postinstall <redacted>/node_modules/react-slick
> opencollective postinstall

sh: <redacted>/node_modules/.bin/opencollective: Permission denied

We don't get this problem with any of our other dependencies.

[qikkeronline]

I am somehow getting this error when running NPM install in a Docker container, but not on my local machine using the exact same Node and NPM versions. Any reason why this can happen? About to start pulling hairs out 😁

[asood123]

can you upgrade to 1.04 please? We had an issue with 1.03.

[asood123]

@kurtinatlanta point noted. :)

[irrg]

@asood123 re: your 1.0.4. comment…I'm interested in getting rid of my opencollective-cli related issues in my nuxt.js environment but 1.0.3 is the latest version published to npm?

[irrg]

I've seen several repos talking about @tsuna 's issue, for what it's worth. Including here nuxt/nuxt#3025

[irrg]

@xdamman awesome, testing in my fork now!

[ralphtheninja]

i'd prefer to not have this dependency at all and not have it run some postinstall script that breaks our builds.

A quick tip is to append || exit 0 to the postinstall script. We use this in level, see https://github.com/Level/level/blob/ddd4a78884ac17648d024df684235070687394a7/package.json#L46

Maybe opencollective could suggest using this by default, or include that when making PRs when enabling open collective for a project?