Skip to content

Impossible typescript Peer Dependencies #1681

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
robodair opened this issue Aug 13, 2016 · 6 comments
Closed

Impossible typescript Peer Dependencies #1681

robodair opened this issue Aug 13, 2016 · 6 comments
Labels
P5 The team acknowledges the request but does not plan to address it, it remains open for discussion type: bug/fix

Comments

@robodair
Copy link

  1. OS?
    Mac OSX El Capitan 10.11.6
  2. Versions.
    angular-cli: 1.0.0-beta.11-webpack.2
    node: 6.3.1
    os: darwin x64
  3. Repro steps. Was this an app that wasn't created using the CLI? What change did you
    do on your code? etc.
    Fresh installation of angular-cli@webpack
  4. The log given by the failure. Normally this include a stack trace and some
    more information.
    screen shot 2016-08-14 at 01 43 54
  5. Mention any other details that might be useful.
    Currently is is impossible to install a version of typescript that pleases all dependencies of the cli. As you can see in the image above, tslint requires >=1.7.3 and @angular/tsc-wrapped requires ^1.9.0-dev (the -dev) preventing it from being a compatible version.

I'm assuming that this will be fixed when typescript 1.9.0 is released fully or updated to 2.0.0 but it's making for a very annoying reminder error. Is one peer dependency required more than another or not required at all?

@Jacob-Friesen
Copy link

Initially I got an error like that, but I upgraded from NPM 2 to NPM 3 and it worked (similar setup, but I am using Node.js 4.4.7). Additionally, I was doing an upgrade from the System JS Angular CLI for an already created app instead of a new app using this document. I still get messages when installing NPM packages like the above, but they are warnings not errors which does not prevent package installations.

So you may want to check if NPM has not been properly upgraded to 3 and upgrade. Not a fix, but at least it may stop the above from being errors.

@filipesilva
Copy link
Contributor

In NPM 3 these are not errors but rather warnings. Unfortunately we didn't specify in the README that NPM 3 is needed, but this is fixed in #1748.

@robodair
Copy link
Author

I should note I'm on NPM 3.10.3

@filipesilva filipesilva reopened this Aug 19, 2016
@filipesilva
Copy link
Contributor

Odd, didn't think this would happen on npm 3. Will investigate more.

@filipesilva filipesilva added type: bug/fix P5 The team acknowledges the request but does not plan to address it, it remains open for discussion labels Aug 19, 2016
@Brocco
Copy link
Contributor

Brocco commented Jan 9, 2017

This issue will be resolved via #3889 closing this issue in favor of that one.

@Brocco Brocco closed this as completed Jan 9, 2017
@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 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P5 The team acknowledges the request but does not plan to address it, it remains open for discussion type: bug/fix
Projects
None yet
Development

No branches or pull requests

4 participants