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

ng new is taking long and failing :( #1270

Closed
pradeepverse opened this issue Jul 2, 2016 · 13 comments
Closed

ng new is taking long and failing :( #1270

pradeepverse opened this issue Jul 2, 2016 · 13 comments

Comments

@pradeepverse
Copy link

pradeepverse commented Jul 2, 2016

  1. OS? Windows 8.1
  2. Versions. Please run ng --version. If there's nothing outputted, please
    run in a Terminal:
    node --version : v6.2.2
    And paste the result here.

(node:6864) fs: re-evaluating native module sources is not supported. If you are
using the graceful-fs module, please update it to a more recent version.
angular-cli: 1.0.0-beta.5
node: 6.2.2
os: win32 x64

  1. Repro steps. Was this an app that wasn't created using the CLI? What change did you
    do on your code? etc.
    NA
  2. The log given by the failure. Normally this include a stack trace and some
    more information.

\ Installing packages for tooling via npm
typings ERR! message Unable to connect
to "https://api.typings.org/entries/dt/angular-protractor/tags/1.5.0%2B201604251
43459"
typings ERR! caused by connect ECONNREFUSED 127.0.0.1:3128

typings ERR! cwd D:\Code\Angular\DynForm
typings ERR! system Windows_NT 6.3.9600
typings ERR! command "C:\Program Files\nodejs\node.exe" "D:\Code\Angular\D
ynForm\node_modules\typings\dist\bin.js" "install"
typings ERR! node -v v6.2.2
typings ERR! typings -v 0.8.1
typings ERR! code EUNAVAILABLE

typings ERR! If you need help, you may report this error at:
typings ERR! https://github.com/typings/typings/issues
dyn-form@0.0.0 postinstall: typings install
Exit status 1
Error: dyn-form@0.0.0 postinstall: typings install
Exit status 1
at EventEmitter. (C:\Users\Pradeepraj.R\AppData\Roaming\npm\node_
modules\angular-cli\node_modules\npm\lib\utils\lifecycle.js:217:16)
at emitTwo (events.js:106:13)
at EventEmitter.emit (events.js:191:7)
at ChildProcess. (C:\Users\Pradeepraj.R\AppData\Roaming\npm\node_
modules\angular-cli\node_modules\npm\lib\utils\spawn.js:24:14)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at maybeClose (internal/child_process.js:852:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)

Kindly help me with this issue.
Thanks

@pradeepverse pradeepverse changed the title ng new is taking long and failing ng new is taking long and failing :( Jul 2, 2016
@filipesilva
Copy link
Contributor

#1250 should fix this issue.

Meanwhile you can run npm install manually by using the --skip-npm flag:

ng new project --skip-npm
cd project
npm install

@kamok
Copy link

kamok commented Aug 8, 2016

Hello,
I just experienced a similar situation.

ng-new was hanging and I ran your --skip-npm method. And it works. I just wanted to let you know because it's suppose to be fixed according to my understanding.

angular-cli: 1.0.0-beta.10
node: 4.4.3
os: win32 x64

npm -v
2.15.1

node -v
v4.4.3

@filipesilva
Copy link
Contributor

@kamok in your case, you might have a problem because you're version of node/npm are somewhat old. We only test on node 5/6, which use npm 3.

@toneware
Copy link

toneware commented Mar 5, 2017

@filipesilva FWIW, it's still an issue.

I'm on Win 10 with a new install of node and angular-cli.

As with @kamok, the --skip-npm workaround does work for me. It's very, very slow (on the order of about half an hour), but it did eventually install.

I ran the Google/M-Lab internet speed test:
47.3 Mbps download
46.0 Mbps upload
Latency: 25 ms
Server: New York, NY
Your Internet speed is fast

Your Internet connection should be able to handle multiple devices streaming HD videos at the same time.

ng -v
As a forewarning, we are moving the CLI npm package to "@angular/cli" with the next release,
which will only support Node 6.9 and greater. This package will be officially deprecated
shortly after.

To disable this warning use "ng set --global warnings.packageDeprecation=false".

                         _                           _  _

__ _ _ __ __ _ _ _ | | __ _ _ __ ___ | |()
/ || '_ \ / _ || | | || | / ` || '|___ / __|| || |
| (
| || | | || (
| || |
| || || (| || | |___|| ( | || |
_
,||| || _, | _,||| _,||| _|||||
|
_/
angular-cli: 1.0.0-beta.28.3
node: 7.7.1
os: win32 x64

npm -v
4.3.0

@filipesilva
Copy link
Contributor

@toneware are you saying that when you do these commands it's fast?

ng new project --skip-npm
cd project
npm install

And when you just do ng new project it's slow?

@toneware
Copy link

toneware commented Mar 6, 2017 via email

@filipesilva
Copy link
Contributor

If even skipping npm and installing it manually takes a long time, then it sounds like there's a problem in your system/connectivity to npm.

I'd also like to mention that in newer releases its not --skip-npm anymore, but rather --skip-install.

@toneware
Copy link

toneware commented Mar 6, 2017 via email

@filipesilva
Copy link
Contributor

I don't think you should need to do that, no... but if npm is giving you problems, you might also try yarn (https://yarnpkg.com/en/).

@toneware
Copy link

toneware commented Mar 7, 2017

I didn't see any real difference between --skip-install and --skip-npm.

How can I use yam from the ng cli?

@filipesilva
Copy link
Contributor

If you do ng new --skip-install (but make sure you're using a recent like 1.0.0-rc.1), the CLI will not install packages for you. Then you can install them manually.

ng new project-name --skip-install
cd project name
yarn install

I can't help you much with the instalation and usage details of yarn itself, for that you should look at their website: https://yarnpkg.com/en/

@kwibus2000
Copy link

Yes! I have tried every trick I could find, but now, finally, this works for me.
Although yarn install still took over 500 seconds! Must be my connection; certainly not 'high-speed'.

@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 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants