fix: cosmiconfig-typescript-loader v5 is not supported on node14

[ImDevinC]

Expected Behavior

Documentation says that node14 is currently supported, however this commit cosmiconfig-typescript-loader adds cosmiconfig-typescript-loader v5 which is not supported on node14 and throws an error when trying to install.

Due to the semver caret being used, this breaks multiple commitlint packages using 17.x.x including commitlint/load and commitlint/cli

Current Behavior

Cannot install on node14

Affected packages

• cli
• core
• prompt
• config-angular

Possible Solution

No response

Steps to Reproduce

1. npm install @commitlint/cli

Context

No response

commitlint --version

@commitlint/cli@17.x.x

git --version

git version 2.39.2 (Apple Git-143)

node --version

v14.20.0

[escapedcat]

Thanks for the issue!
Pity the tests didn't catch this one. I guess we'll roll this back and keep this for the next major-version then.
wdyt @joberstein ?

[escapedcat]

Should be fixed in this new release: https://github.com/conventional-changelog/commitlint/releases/tag/v17.7.1

[joberstein]

Thanks for the issue! Pity the tests didn't catch this one. I guess we'll roll this back and keep this for the next major-version then. wdyt @joberstein ?

Sure, sorry about that. I saw the breaking change in their docs, but was a little too reliant on the test matrix 😅 and thought a feature bump was enough. I think node 14 is already in EOL, would it make sense to move to v18 in that case or is there a specific cadence for major releases?

[escapedcat]

Sure, sorry about that. I saw the breaking change in their docs, but was a little too reliant on the test matrix 😅

:D No worries, same here. Not sure if the test could be adjusted to catch something like this. Or if it's not worth the effort.

I think node 14 is already in EOL, would it make sense to move to v18 in that case or is there a specific cadence for major releases?

In the case of node versions we usually do a mayor release if a version is EOL. So ditching v14 would be the next step. We usually keep support for the maintenance version (v16 in this case). Would prepare this during the next days.

Closing this issue for now then.