since the hapi packages are now all scoped, using the latest @hapi/hapi fails to meet the defined peer-dependency on hapi. off the top of my head, i'm not aware of a way to set a peer to expect either/or.
what would you say to making a breaking release that changed the peer-dependency from "hapi": ">=17.x.x" to "@hapi/hapi": ">=18.x.x"?
since you mentioned possibly bringing on more maintainers, i should also mention that i'm willing to help out or take over maintenance if you'd find either option helpful to you.
since the hapi packages are now all scoped, using the latest
@hapi/hapi
fails to meet the defined peer-dependency onhapi
. off the top of my head, i'm not aware of a way to set a peer to expect either/or.what would you say to making a breaking release that changed the peer-dependency from
"hapi": ">=17.x.x"
to"@hapi/hapi": ">=18.x.x"
?