Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

npm install fails during create-nx-workspace #238

Closed
olakara opened this issue Jan 28, 2018 · 6 comments
Closed

npm install fails during create-nx-workspace #238

olakara opened this issue Jan 28, 2018 · 6 comments
Labels

Comments

@olakara
Copy link

olakara commented Jan 28, 2018

I have the following installed on my PC:
Angular CLI: 1.6.2
Node: 8.6.0
OS: win32 x64
npm: 5.3.0

I installed schematics through the command: npm install -g @nrwl/schematics and completed successfully. Next, I ran: create-nx-workspace my which didn't complete and threw the following error:

Error: Command failed: npm install --silent at checkExecSyncError (child_process.js:592:13) at Object.execSync (child_process.js:632:13)

Here is the screenshot:
untitled

the command keeps throwing error at child_process.js. I am not able to see the partially created workspace to manually try the npm install command as well. Any solution to this issue? Anybody else facing this?

@sandangel
Copy link

take > 10minutes on macos too

I'm using nx/schematics 0.6.19

@jeffkenz89
Copy link

try use yarn

@dereklin
Copy link

dereklin commented Feb 1, 2018

This happens to me when I am behind proxy. use --yarn shows this error:

error ".angular_cli165.tgz": Tarball is not in network and can not be located in cache ...

Need to figure out how to properly set the proxy for this...

@jeffbcross
Copy link
Member

I saw this, too. I think it's because this line should be tmpDir instead of '.', right @vsavkin?

@vsavkin
Copy link
Member

vsavkin commented Feb 19, 2018

The issue has been fixed here: cc3f51f

@vsavkin vsavkin closed this as completed Feb 19, 2018
@github-actions
Copy link

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants