You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The duplicate npm commands in the documentation draw my attention and I saw some of the CLI commands uses the @commitlint/{cli,config-conventional} syntax. In the case of npm (for Windows), however, it uses the good old verbose one (@commitlint/cli @commitlint/config-conventional).
However, this differentiation does not only apply to npm, but for other package managers like yarn and pnpm in Windows as well. So, for simplification and consistency, I'd suggest defining a single command for each package manager and use the syntax compatible across operating systems.
The text was updated successfully, but these errors were encountered:
…based systems (#4381) (#4382)
* docs: fix JSON syntax
* docs: adjust package managers CLI instructions for both Win and Unix based systems (#4381)
* docs: fix CLI instruction not compatible to Windows
* docs: adjust markdown
The duplicate
npm
commands in the documentation draw my attention and I saw some of the CLI commands uses the@commitlint/{cli,config-conventional}
syntax. In the case ofnpm (for Windows)
, however, it uses the good old verbose one (@commitlint/cli @commitlint/config-conventional
).However, this differentiation does not only apply to
npm
, but for other package managers likeyarn
andpnpm
in Windows as well. So, for simplification and consistency, I'd suggest defining a single command for each package manager and use the syntax compatible across operating systems.The text was updated successfully, but these errors were encountered: