Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Commitlint broken due to minimist upgrade

See original GitHub issue

Expected Behavior

Commitlint works

Current Behavior

Commitlint doesn’t work

Affected packages

Possible Solution

Patch default values of the flags so default types match flag types (https://github.com/marionebl/commitlint/blob/master/%40commitlint/cli/src/cli.js#L16)

Steps to Reproduce (for bugs)

Install commitlint
Run git commit
See TypeError: Expected "config" default value to be string, got object

Context

Here is an PR on the minimist https://github.com/vadimdemedes/minimist-options/pull/8

Your Environment

Executable	Version
`commitlint --version`	7.3.2

Issue Analytics

State:
Created 5 years ago
Comments:13 (7 by maintainers)

Top GitHub Comments

2reactions

bniedermeyercommented, May 2, 2019

@byCedric No problem - thanks for your help. Just to clarify the procedure to fix this for those with private registries should be:

purge the bad version from the cache
reinstall so the fix is picked up by the registry

0reactions

byCedriccommented, May 6, 2019

@bniedermeyer yes, that’s it! Remove it from the private registry and it should resolve the (working)-older version. 😄 Good luck and let us know if we can help more! 😄

Top Results From Across the Web

@commitlint/read | Yarn - Package Manager

Fast, reliable, and secure dependency management.

Update to esLint on Angular breaks commitlint - Stack Overflow

I just updated an Angular 11 app to eslint and installed commitizen, commitlint, husky and semantic-release to drive CI through npm and ...

commitlint - Bountysource

I'm trying to commit in a new repository that uses husky and my commit should work and pass husky checks as expected. Current...

Compare Versions | @elliemae/pui-cli | npm

GHSA-vh95-rmgr-6w4mPrototype Pollution in minimist ... GHSA-3jfq-g458-7qm9Arbitrary File Creation/Overwrite due to insufficient absolute path sanitization.

Fixing security vulnerabilities in npm dependencies in less ...

Have you considered running `npm update minimist — depth 6` . ... This does fix the vulnerability issue, but when I run npm...