Nest: Opencollective and no network

[anthonybriand]

I'm submitting a...

[ ] Regression 
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

After the installation of NestJS it calls the opencollective binary but if there is no network the installation fails.

Expected behavior

The installation doesn't fails if there is no network

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

I need the possibility of an offline installation based on a NPM cache.

Environment

Nest version: 5.3.7


For Tooling issues:
- Node version: 9.7.1  
- Platform: Mac and Linux 

[kamilmysliwiec]

Hi @anthonybriand,
See here: https://github.com/nuxt-community/opencollective#disable-message
simply set NODE_ENV (not dev or development) or any other mentioned environment variable like, for example, CI

[ondrej-osnet-cz]

Just note for others:
On Linux (Ubuntu server in my case) you also need has set X flag permission (permission to execute) on folder where you ran npm install. Otherwise it crash on opencollective unknown command.
I think this wasn`t necessary in previous versions of nestjs framework.

[kamilmysliwiec]

Reopening

[kamilmysliwiec]

The error shouldn't break the build now (in latest patch version @nestjs/[email protected])

[ktanakaj]

My issue (#1110) is not same but almost like.
I guess the postinstall script can't call opencollective command because --no-bin-links option doesn't create symlinks to node_modules/.bin executables directory.

I think the script is not required. It is optional.
The script may skip when the command is not available.

[kamilmysliwiec]

@ktanakaj could you check if the install is still failing for your case with the latest version (@nestjs/[email protected])?

[ktanakaj]

@kamilmysliwiec Oh, thanks!
I succeeded install with --no-bin-links option now.
Thanks for your quick action.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.