You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 20, 2019. It is now read-only.
Hi, we were hoping to upgrade from Hapi 11 to 13 and receive the following error running npm install:
npm ERR! Darwin 15.5.0
npm ERR! argv "/Users/bflad/.nvm/versions/node/v4.4.1/bin/node" "/Users/bflad/.nvm/versions/node/v4.4.1/bin/npm" "install"
npm ERR! node v4.4.1
npm ERR! npm v2.14.20
npm ERR! code EPEERINVALID
npm ERR! peerinvalid The package hapi@13.4.1 does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer reptile@2.1.1 wants hapi@>=11.x.x
The peerDependencies are currently too strict to support both 11 and 13:
"peerDependencies": {
"hapi": ">=11.x.x"
},
I noticed you already have 13.x.x in the devDependencies, are you planning on cutting a release with 13 support? Please let me know if you need any help testing or upgrading. Thanks!
The text was updated successfully, but these errors were encountered:
@geek I don't think this was an issue. 13.x.x satisfies >=11.x.x, but one of my apps on hapi v11 becomes sad when pulling in this change due to a peer dep error.
Interestingly enough, NPM was listing all modules with hapi as a peer dependency for these peerDependencies errors. Another module updated its dependency from ~11.x.x to allow both 11 and 13, then without upgrading this module, NPM was happy. It looks like >=11.x.x should actually work for 11 and 13. I'm really sorry for the confusion here.
Hi, we were hoping to upgrade from Hapi 11 to 13 and receive the following error running
npm install
:The peerDependencies are currently too strict to support both 11 and 13:
I noticed you already have 13.x.x in the devDependencies, are you planning on cutting a release with 13 support? Please let me know if you need any help testing or upgrading. Thanks!
The text was updated successfully, but these errors were encountered: