Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

unmet peer dependency with angular4

See original GitHub issue

Bug, feature request, or proposal:

A problem

What is the expected behavior?

Flawless installation

What is the current behavior?

Unmet peer dependencies with higher versions of demanded dependencies resulting in failing installation

What are the steps to reproduce?

Use these angular dependencies in package.json:

    "@angular/animations": "^4.1.3",
    "@angular/common": "^4.1.3",
    "@angular/compiler": "^4.1.3",
    "@angular/compiler-cli": "^4.1.3",
    "@angular/core": "^4.1.3",
    "@angular/forms": "^4.1.3",
    "@angular/http": "^4.1.3",
    "@angular/platform-browser": "^4.1.3",
    "@angular/platform-browser-dynamic": "^4.1.3",
    "@angular/platform-server": "^4.1.3",
    "@angular/router": "^4.1.3",

What is the use-case or motivation for changing an existing behavior?

I need to use this particular version of angular.

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

Angular 4.1.3 and the newest material

Is there anything else we should know?

http://i.imgur.com/p7u2kDI.png http://i.imgur.com/JACGk3F.png

Issue Analytics

State:
Created 6 years ago
Reactions:1
Comments:8 (3 by maintainers)

Top GitHub Comments

1reaction

pstephenwillecommented, Nov 5, 2017

@jelbourn Why did you close this? I have this issue and I don’t see it resolve anywhere.

1reaction

jelbourncommented, Jun 28, 2017

@spartanPAGE Try wiping away your node_modules and package-lock.json. I suspect this is a problem with your environment. The package.json for the latest release lists deps at ^4.0.0, which ^4.1.3 satisfies. So either a problem with npm (old version?) or with your environment.