Skip to content

ng new is failing #1272

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

Closed
indcoder opened this issue Jul 3, 2016 · 3 comments
Closed

ng new is failing #1272

indcoder opened this issue Jul 3, 2016 · 3 comments

Comments

@indcoder
Copy link

indcoder commented Jul 3, 2016

Please provide us with the following information:

  1. OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
    Windows 10 Pro
  1. Versions. Please run ng --version. If there's nothing outputted, please
    run in a Terminal:
    node --version
    And paste the result here.
    v6.2.2
  2. Repro steps. Was this an app that wasn't created using the CLI? What change did you
    do on your code? etc.
    ng new create
  3. The log given by the failure. Normally this include a stack trace and some
    more information.

unzip error C:\Users\indcoder\AppData\Local\Temp\npm-10796-b2a49a97\registry.npmjs.org\esprima-fb-\esprima-fb-15001.1001.0-dev-harmony-fb.tgz
unzip error C:\Users\incoder\AppData\Local\Temp\npm-10796-b2a49a97\registry.npmjs.org\iconv-lite-\iconv-lite-0.4.13.tgz
unexpected end of file
Error: unexpected end of file
at Zlib._handle.onerror (zlib.js:370:17)

  1. Mention any other details that might be useful.

Also i think some files, during install, are nested so deep that it is exceeding Windows maximum file name limitation
C:\Users\INCODE1\DOWNLO1\GitHub\DOCKER2\NODE_M1\ANGULA1\NODE_M1\EMBER-2\NODE_M1\BRA4211\NODE_M1\BABEL-1\NODE_M1\REGENE1\NODE_M1\defs\NODE_M1\yargs\NODE_M1\cliui\NODE_M1\CENTER1\NODE_M1\ALIGN-1\NODE_M1\kind-of\NODE_M1\is-buffer\test


Thanks! We'll be in touch soon.

@filipesilva
Copy link
Contributor

Dupe of #1186.

@filipesilva
Copy link
Contributor

@indcoder I know it doesn't sound like the same issue, but it stems from the same root and #1250 fixes it.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants