peerDependencies versions are too specific

[3fd]

I'm submitting a...

[ ] Regression 
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

Whenever a peer dependency version doesn't match the installed version exactly, npm displays warnings:

npm WARN @nestjs/terminus@6.5.1 requires a peer of @godaddy/terminus@4.1.2 but none is installed. You must install peer dependencies yourself.
npm WARN @nestjs/terminus@6.5.1 requires a peer of @nestjs/common@6.5.3 but none is installed. You must install peer dependencies yourself.
npm WARN @nestjs/terminus@6.5.1 requires a peer of @nestjs/core@6.5.3 but none is installed. You must install peer dependencies yourself.
npm WARN @nestjs/terminus@6.5.1 requires a peer of rxjs@6.5.2 but none is installed. You must install peer dependencies yourself.

Expected behavior

No warnings should be displayed for compatible peer dependency versions.

The version range for peer dependencies should be as wide as possible. It should at least include patch or minor versions.

Environment

Nest version: 6.6.7
@nestjs/terminus version: 6.5.1
@godaddy/terminus: 4.2.0
rxjs 6.5.3

 
For Tooling issues:
- Node version: 12.2.0 
- Platform: Linux 

Others:
- NPM version: 6.11.2

[BrunnerLivio]

Thanks! Fixed it, will publish asap