Opencollective install issues

Hello,

Since adding this component to our project I can no longer build on azure. Apparently there is some bug with opencollective post install. npm ls shows that ngx-infinate-scroll is the only thing depending on that. I get the same error as here: https://github.com/opencollective/opencollective-cli/issues/8

npm ERR! code EBUSY npm ERR! errno -4082 npm ERR! syscall rename npm ERR! EBUSY: resource busy or locked, rename 'D:\home\site\wwwroot\node_modules\opencollective\dist\bin\opencollective.js.3840949171' -> 'D:\home\site\wwwroot\node_modules\opencollective\dist\bin\opencollective.js'

The open collective people say they published a lightwieght version: https://github.com/opencollective/opencollective-cli/issues/3 https://github.com/opencollective/opencollective-postinstall

I dont suppose ngx-infinite-scroll could be updated to use that lightweight version?

[jcroll]

@orizens I’ve been trying to bite my tongue but have been continually running into this error over the past couple weeks after upgrading your package:

npm ERR! path /usr/share/frontend/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 '/usr/share/frontend/node_modules/opencollective/dist/bin/opencollective.js'

I foresee having to fork your library if you don’t remove this unnecessary dependency, it’s hard to justify the development hours working around it.

There’s apparently another solution from opencollective (cli or something) but I read somewhere you didn’t like it.

This opencollective thing makes a great third party library like yours difficult to work with, please consider removing it. Thanks for your time

[thescientist13]

ok, thanks @orizens !

Will be glad to take a look on our end this week and report back (or open a PR) if we can help out!