Skip to content

Cannot create any project #1146

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
frodefi opened this issue Jun 20, 2016 · 4 comments
Closed

Cannot create any project #1146

frodefi opened this issue Jun 20, 2016 · 4 comments

Comments

@frodefi
Copy link

frodefi commented Jun 20, 2016

Using OSX 10.11.5, Node 4.4.5, npm 3.10.1 and [email protected].

When I try to create a new project with something like ng new my-dream-app, I get the following error before the cli hangs:
Installing packages for tooling via npmtypings ERR! message Unknown dependency: registry:dt/es6-shim#0.31.2+20160317120654

When the cli hangs, the internet is not working either. Maybe because it is related to this npm issue?

@hacknaked
Copy link

According to https://angular.io/docs/ts/latest/quickstart.html#!#prereq
Angular 2 requires at least node v5.x.x and npm 3.x.x. So I'd recommend to upgrade your Node to v6.x (the next LTS version).

@frodefi
Copy link
Author

frodefi commented Jun 20, 2016

Upgraded to node 6.2.2 with npm 3.9.5, same problem :(

DigitalWife:t2 ff$ node --version
v6.2.2
DigitalWife:t2 ff$ npm --version
3.9.5
DigitalWife:t2 ff$ sudo npm install -g angular-cli
/usr/local/bin/ng -> /usr/local/lib/node_modules/angular-cli/bin/ng
- [email protected] node_modules/angular-cli/node_modules/rewire
/usr/local/lib
└── [email protected] 

DigitalWife:t2 ff$ ng new blisteinrik
(node:1216) 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.
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
installing ng2
  create .editorconfig
  create README.md
  create src/app/app.component.css
  create src/app/app.component.html
  create src/app/app.component.spec.ts
  create src/app/app.component.ts
  create src/app/environment.ts
  create src/app/index.ts
  create src/app/shared/index.ts
  create src/favicon.ico
  create src/index.html
  create src/main.ts
  create src/system-config.ts
  create src/tsconfig.json
  create src/typings.d.ts
  create angular-cli-build.js
  create angular-cli.json
  create config/environment.dev.ts
  create config/environment.js
  create config/environment.prod.ts
  create config/karma-test-shim.js
  create config/karma.conf.js
  create config/protractor.conf.js
  create e2e/app.e2e-spec.ts
  create e2e/app.po.ts
  create e2e/tsconfig.json
  create e2e/typings.d.ts
  create .gitignore
  create package.json
  create public/.npmignore
  create tslint.json
  create typings.json
⠋ Installing packages for tooling via npmtypings ERR! message Unknown dependency: registry:dt/es6-shim#0.31.2+20160317120654

typings ERR! cwd /Users/ff/Google Drive/Developing/t2/blisteinrik/node_modules/@angular/router
typings ERR! system Darwin 15.5.0
typings ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/typings/dist/bin/typings-install.js"
typings ERR! node -v v6.2.2
typings ERR! typings -v 0.6.2

typings ERR! If you need help, you may report this error at:
typings ERR!   <https://github.com/typings/typings/issues>

⠋ Installing packages for tooling via npm

@filipesilva
Copy link
Contributor

This might be related to #1092 actually, or even a dupe.

In beta.6, one of the installed dependencies has a typings install hook, which unfortunately uses the global typings. In your case, I would say that your global typings is a pre-1.0.0 version that has trouble with the new registry formats.

This will be fixed in beta.7, which should come out soon. Meanwhile, you can follow #1092 (comment) to get it working.

@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.
Projects
None yet
Development

No branches or pull requests

3 participants