Skip to content

dependency problem with ng new #1238

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
burhan opened this issue Jun 29, 2016 · 8 comments
Closed

dependency problem with ng new #1238

burhan opened this issue Jun 29, 2016 · 8 comments
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful type: bug/fix

Comments

@burhan
Copy link

burhan commented Jun 29, 2016

I am running this on Ubuntu 16.04 LTS; and following the steps from the Google IO 2016 talk, I entered the following command:

ng new puppy-love-io --mobile

It seems there is an issue with dependencies:

Successfully initialized git.
⠼ Installing packages for tooling via npm
├── es6-shim (ambient)
├── node (ambient)
├── angular-protractor (ambient dev)
├── jasmine (ambient dev)
└── selenium-webdriver (ambient dev)

The package @angular/[email protected] does not satisfy its siblings' peerDependencies requirements!
Error: The package @angular/[email protected] does not satisfy its siblings' peerDependencies requirements!
    at /usr/lib/node_modules/angular-cli/node_modules/angular-cli/node_modules/npm/lib/install.js:125:32
    at /usr/lib/node_modules/angular-cli/node_modules/angular-cli/node_modules/npm/lib/install.js:268:7
    at /usr/lib/node_modules/angular-cli/node_modules/angular-cli/node_modules/npm/node_modules/read-installed/read-installed.js:142:5
    at /usr/lib/node_modules/angular-cli/node_modules/angular-cli/node_modules/npm/node_modules/read-installed/read-installed.js:263:14
    at cb (/usr/lib/node_modules/angular-cli/node_modules/angular-cli/node_modules/npm/node_modules/slide/lib/async-map.js:47:24)
    at /usr/lib/node_modules/angular-cli/node_modules/angular-cli/node_modules/npm/node_modules/read-installed/read-installed.js:263:14
    at cb (/usr/lib/node_modules/angular-cli/node_modules/angular-cli/node_modules/npm/node_modules/slide/lib/async-map.js:47:24)
    at /usr/lib/node_modules/angular-cli/node_modules/angular-cli/node_modules/npm/node_modules/read-installed/read-installed.js:263:14
    at cb (/usr/lib/node_modules/angular-cli/node_modules/angular-cli/node_modules/npm/node_modules/slide/lib/async-map.js:47:24)
    at /usr/lib/node_modules/angular-cli/node_modules/angular-cli/node_modules/npm/node_modules/read-installed/read-installed.js:263:14

Pertinent version information:

$ node -v && npm -v && ng --version
v6.2.2
3.10.2
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
angular-cli: 1.0.0-beta.8
node: 6.2.2
os: linux x64
@dylclem
Copy link

dylclem commented Jul 2, 2016

having same error but with osx 10.11.5

@filipesilva filipesilva added type: bug/fix P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful labels Jul 3, 2016
@mackelito
Copy link

#958 same issue?

@tmguimaraes
Copy link

same error with Windows 10

@71be7
Copy link

71be7 commented Jul 12, 2016

Had the same issue and it fixed by:
npm uninstall -g angular-cli
npm install -g angular-cli@latest

@mackelito
Copy link

@WimpyKnight are you really running the --mobile flag?

@tmguimaraes
Copy link

tmguimaraes commented Jul 13, 2016

@WimpyKnight tried that, it gave me a Cannot read property 'makeCurrent' of undefined when doing ng serve.
You probably didn't test with --mobile

@filipesilva
Copy link
Contributor

Closed as issue was made obsolete by #1455.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
@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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful type: bug/fix
Projects
None yet
Development

No branches or pull requests

6 participants