Ngx-infinite-scroll: Opencollective install issues

[spacem]

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?

[orizens]

hi @spacem
as far as i understood, it's not possible to trigger the contribute notice without it.

[Prashanth-Arralli]

@spacem Found any solution for this problem ?

[spacem]

Really it is Microsoft's fault since their file pointers are weird. Or maybe it is their directory entries? In other operating systems renaming a directory entry does not require a lock on the file but that is how windows has always been so I guess node.js applications are not multi-platform by default.

I do feel the open collective people are partially to blame. I don't donate financially to open source but I don't think much of companies that take a cut of donations. At least they made the postinstall version but not sure what orizens means that it wont trigger the contrib notice. I thought that was the point of it?

There are a few solutions if you hit this same problem:

• Don't deploy your application
• Don't use windows
• Build the application before deployment
• Fork this infinite scroll library and remove the dependency
• Don't use infinite scroll

Those are in my personal order of preference.. ie. for now I choose just not to deploy my application. It is still in development and I am hoping the problem will just go away on its own.

Anyway thanks for the library and feel free to close my issue if you want.

[bharathmuppa]

@orizens If that is not a bug then what in the world is that? please dont keep it as dependencies please donate to open source world.

[thescientist13]

Hey @orizens
There seems to be another related issue on this as well and acknowledgement here.

In addition to the error about missing opencollective the instructions also require opencollective setup to be run so I can foresee this not quite working out the way it might have been intended, in particular for CI servers where this minimal opportunity for manual intervention.

Is there anyway to improve the developer experience for this? Let me know, I can help open a PR for whatever a viable solution might be.

[orizens]

hi @thescientist13
i have my project http://github.com/orizens/echoes-player deployed from travis-ci without any issues.
I'de be happy to see a relevant pr which keeps opencollective and address the issue - if the issue can is in this repository.
btw, ngrx/store is using the same opencollective - so might be worth checking it out there.

[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!

[Marcidius]

Any movement on this?

[thescientist13]

the need to upgrade to the newer version hasn't presented itself to me again, so haven't looked into this unfortunately.

[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

[orizens]

fixed with 7.1.0

[jcroll]

Nice!

[jcroll]

Confirmed, much better thanks @orizens