@commitlint/cli@17.1.1 throws on load of javascript config missing ts-node

Running commitlint with a js config fails for me since today on CI as the load module needs ts-node package, but doesn't find it. I can reproduce it locally.

Expected Behavior

Expected to be able to run commitlint on configs without typescript and without installing additional packages manually.

Current Behavior

Loader fails to run, requires to install ts-node manually.

Affected packages

• cli
• core
• prompt
• config-angular

Steps to Reproduce (for bugs)

• Config
• CI Job
• Failed pipeline

[escapedcat]

This was introduced with updating cosmiconfig-typescript-loader/releases:
https://github.com/Codex-/cosmiconfig-typescript-loader/releases/tag/3.0.0

We need the ts-loader for this: https://github.com/conventional-changelog/commitlint/blob/master/@commitlint/load/src/utils/load-config.ts#L30-L36

The ts-node dependency has been discussed here as well: #3221
Now the problem is very transparent.

Not sure how to deal with this best. Happy for feedback, suggestions, PRs.

Easiest way might just be to re-add it as a dep and push out a new version.

[Harukisatoh]

Is there any workaround that we can do for now while the package is not updated yet?

Is there any workaround that we can do for now while the package is not updated yet?

You should be able to make it work by installing the ts-node package manually.

Not sure how to deal with this best. Happy for feedback, suggestions, PRs.

Is it possible that commitlint only tries to find the ts-node module when reading a typescript config and otherwise not even looks for it?

[Harukisatoh]

Is there any workaround that we can do for now while the package is not updated yet?

You should be able to make it work by installing the ts-node package manually.

Thanks man. But I preferred to just downgrade the lib to v16.3.0 for now as my project is not a Typescript one.

[escapedcat]

Fixed with: https://github.com/conventional-changelog/commitlint/releases/tag/v17.1.2
Thanks @filiptammergard !