Same problem here !
Is there a way to make the shrinkwrap work with the peerDependencies ?

I will add a 1 to this. It should just be a warning.

I need a workaround now....

is there any workaround, for this scenario

The best would be to just install the missing dep.

i have a package where a listed dependency is out of date, and we are using a more up-to-date version of that dependency. unfortunately shrinkwrap gives us trouble and wants us to list the more out-of-date version in our package.json. would love to be able to ignore the requirement somehow.

I'm seeing this with a package that lists Angular 2 as a peer dependency when I use Angular 4. I've tried updating the dependency of the package to "@angular/core": "^2.0.0 <=4.0.2" but that errors out as well.

@iammikecohen "@angular/core": "^2.0.0 <=4.0.2" is effectively the same as "@angular/core": "^2.0.0" or "@angular/core": ">=2.0.0 <3" so you're using Angular 2, not 4 then.

https://semver.npmjs.com/ can help you to figure out semver ranges.

@mgol Thank you, I should have been using "@angular/core": "^2.2.0 || ~4.0.0"

We're closing this issue as it has gone seven days without activity and without being labeled. If we haven't even labeled in issue in seven days then we're unlikely to ever read it.

If you are still experiencing the issue that led to you opening this or this is a feature request you're still interested in then we encourage you to open a new issue. If this was a support issue, you may be better served by joining package.communty and asking your question there.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

@mgol How did you end up solving this?

@Rovack I haven't. The only projects in which I used npm shrinkwrap are non-public company projects that have since migrated to Yarn.

I haven't tested it recently but I assume the issue is still there.

It definitely is. Quite surprising, then, that all issues opened around this (e.g this and this) seem to have been closed with no resolution.
Perhaps the assumption is that no projects use shrinkwrap anymore...

Issue is definitely still happening shrinkwrap is still enforcing peerDependencies that are only a warning on install

I'm going to bump this so the dumbass npm issue bot doesn't auto close it. Using npm 4.6.1 and I can't shrinkwrap since it doesn't ignore the peerDependency warning. It's isn't so that I'm missing the dependency even it's just the package I'm using has stupid strict peerDependency versions.

I'm also having issues to shrinkwrap when peer dependencies of third parties doesn't get fullfilled.

1 on the issue. npm shrinkwrap fails with invalid peer dependency on transitive dependencies

Having the same issues with npm shrinkwrap

same.

npm ERR! Problems were encountered
npm ERR! Please correct and try again.
npm ERR! peer invalid: popper.js@^1.11.0, required by [email protected]
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues

npm ERR! Please include the following file with any support request:
npm ERR! c:\Users\peters1\bench\um_kb\npm-debug.log

1

npm ERR! Linux 3.13.0-129-generic
npm ERR! argv "/opt/nvm/versions/node/v6.10.3/bin/node" "/opt/nvm/versions/node/v6.10.3/bin/npm" "shrinkwrap"
npm ERR! node v6.10.3
npm ERR! npm  v3.10.10

npm ERR! Problems were encountered
npm ERR! Please correct and try again.
npm ERR! peer invalid: webpack@^1.12.13 || ^2.1.0-beta.15, required by [email protected]
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /var/www/gousto2frontend/src/npm-debug.log

Hi guys, I am facing the same problem as @garethtalty .
Someone knows how to fix this issue?

1

1 Exactly the same issue as @httpete

1