Peer dependency warnings for @types/node

Depending on @commitlint/prompt or @commitlint/cli results in peer dependency warnings because the @types/node peer dependency of cosmiconfig-typescript-loader is not satisfied in @commitlint/load

Depending on @commitlint/prompt or @commitlint/cli should not result in any peer dependency warnings.

Depending on @commitlint/prompt or @commitlint/cli results in peer dependency warnings.

Affected packages

• cli
• core
• prompt
• config-angular

Possible Solution

Either expose @types/node as a peer dependency of @commitlint/load and then of @commitlint/cli and @commitlint/prompt, or add @types/node as a dependency of @commitlint/load.

I’d be happy to open a pull request for this, but am curious if there’s a preference as to how we resolve this (see above).

Steps to Reproduce (for bugs)

1. yarn init
2. yarn add @commitlint/cli

Context

Consolidate all JavaScript tooling into a single package https://github.com/hoverinc/hover-javascript/

Your Environment

Executable	Version
commitlint --version	16.1.0
git --version	1.33.0
node --version	16.13.0

[jrolfs]

Maybe also align the versions when you are on it anways. Looks like we have these two different versions atm:

“@types/node”: “^12.20.27”, “@types/node”: “12.20.43”,

I guess these could just be the same.

Also, I use manypkg in my monorepos to keep dependencies aligned. I could open another PR to add that here but there a quite a few fixes it would make:

[escapedcat]

so maybe adding it as a direct dependency of @commitlint/load with a permissive range would be the best solution?

Got it, sounds good to me. Wanna give it a try?