Skip to content

UNMET PEER DEPENDENCY [email protected] #1737

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
281330 opened this issue Aug 18, 2016 · 10 comments
Closed

UNMET PEER DEPENDENCY [email protected] #1737

281330 opened this issue Aug 18, 2016 · 10 comments

Comments

@281330
Copy link

281330 commented Aug 18, 2016

Please provide us with the following information:

  1. OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
    Linux Mint
  2. Versions. Please run ng --version. If there's nothing outputted, please run
    in a Terminal: node --version and paste the result here:
    1.0.0-beta.11-webpack.2
  3. Repro steps. Was this an app that wasn't created using the CLI? What change did you
    do on your code? etc.
    This is an app created using angular-cli. All I am doing is running npm install
  4. The log given by the failure. Normally this include a stack trace and some
    more information.
    UNMET PEER DEPENDENCY [email protected]
  5. Mention any other details that might be useful.

Thanks! We'll be in touch soon.

Here's the result of npm list typescript

├─┬ [email protected]
│ └─┬ [email protected]
│   └── [email protected] 
└── UNMET PEER DEPENDENCY [email protected]

npm ERR! peer dep missing: typescript@^1.9.0-dev, required by @angular/[email protected]
@mangopop
Copy link

mangopop commented Aug 18, 2016

angular-cli: 1.0.0-beta.11-webpack.2
node: 4.4.3
os: win32 x64 windows 10
ng init
I'm getting the same

@neilhem
Copy link
Contributor

neilhem commented Aug 18, 2016

Hi, something does not work? I have the same warning, but app runs fine.

@mangopop
Copy link

Just done some testing and the app does seem to run ok.

@kylecordes
Copy link

I think this is a spurious message because of unfixed messiness in the various underlying libraries. Once the versions stabilize (i.e.. the various libraries are updated and reconciled to agree on what TypeScript version they want), these messages should go away. In the meantime, I've been using TypeScript 2.0.0 and getting good results, while ignoring messages that complain about an UNMET PEER DEPENDENCY for something that is sitting right there...

@alo
Copy link

alo commented Aug 19, 2016

+1

@filipesilva
Copy link
Contributor

Peer dependency warning will be around for a bit while the ecosystem adapts to the new Typescript and Node versions.

They should be warnings however, not errors - try updating to NPM3 and they should be listed as warnings.

@lindsaymarkward
Copy link

I have npm3 but these show as ERRors not warnings:

➜  ng-challenge git:(master) ✗ npm --version
3.10.6
➜  ng-challenge git:(master) ✗ npm list typescript
[email protected] /Users/sci-lmw1/Documents/dev/ng-challenge
├─┬ [email protected]
│ └─┬ [email protected]
│   └── [email protected] 
└── UNMET PEER DEPENDENCY [email protected]

npm ERR! peer dep missing: typescript@^1.9.0-dev, required by @angular/[email protected]

Am I missing something, or do I still just ignore this?

@iBasit
Copy link

iBasit commented Sep 8, 2016

same here...

@neilhem
Copy link
Contributor

neilhem commented Sep 8, 2016

Try to update to the latest version [email protected]

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

No branches or pull requests

8 participants