question-mark
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.

[BUG] Extenstion stopped recognizing commitlint rules

See original GitHub issue

Describe the bug Since yesterday the extension stopped recognizing configured scopes and other settings for me and my colleagues. Unfortunately I have no idea why, nothing has changed about the setup of the repository or the configurations themselves. Have there been any recent changes to the extensions which may have caused it? The last working version for us seems to be 1.16.1.

Application logs

Activated
vscode.env.language: en
[warning] getNLS: Missing translation for en
Started
VSCode version: 1.54.3
VSCode Conventional Commits version: 1.18.0
Git version: 1.0.0
autoCommit: true
gitmoji: false
emojiFormat: code
scopes: 
lineBreak: 
promptScopes: true
git.enableSmartCommit: true
git.smartCommitChanges: all
git.postCommitCommand: none
arg: undefined
git.repositories: /home/redacted
workspaceFolders: /home/redacted
commitlintRuleConfigs: {}

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:14 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
avendiartcommented, Mar 26, 2021

Still the same issue:

[error] commitlint: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
	at validateString (internal/validators.js:120:11)
	at Object.dirname (path.js:1128:5)
	at module.exports (/home/user/.vscode-server/extensions/vivaxy.vscode-conventional-commits-1.18.2-88f5531/dist/extension.js:21951:37)
	at loadJs (/home/user/.vscode-server/extensions/vivaxy.vscode-conventional-commits-1.18.2-88f5531/dist/extension.js:2679:18)
	at Explorer.loadFileContent (/home/user/.vscode-server/extensions/vivaxy.vscode-conventional-commits-1.18.2-88f5531/dist/extension.js:2140:32)
	at Explorer.createCosmiconfigResult (/home/user/.vscode-server/extensions/vivaxy.vscode-conventional-commits-1.18.2-88f5531/dist/extension.js:2145:36)
	at Explorer.loadSearchPlace (/home/user/.vscode-server/extensions/vivaxy.vscode-conventional-commits-1.18.2-88f5531/dist/extension.js:2126:31)
	at async Explorer.searchDirectory (/home/user/.vscode-server/extensions/vivaxy.vscode-conventional-commits-1.18.2-88f5531/dist/extension.js:2111:27)
	at async run (/home/user/.vscode-server/extensions/vivaxy.vscode-conventional-commits-1.18.2-88f5531/dist/extension.js:2091:22)
	at async cacheWrapper (/home/user/.vscode-server/extensions/vivaxy.vscode-conventional-commits-1.18.2-88f5531/dist/extension.js:2471:18)
	at async Explorer.search (/home/user/.vscode-server/extensions/vivaxy.vscode-conventional-commits-1.18.2-88f5531/dist/extension.js:2083:20)
	at async Object.loadConfig (/home/user/.vscode-server/extensions/vivaxy.vscode-conventional-commits-1.18.2-88f5531/dist/extension.js:1851:19)
	at async Object.load [as default] (/home/user/.vscode-server/extensions/vivaxy.vscode-conventional-commits-1.18.2-88f5531/dist/extension.js:21612:18)
[info] commitlintRuleConfigs:
{}
1reaction
vivaxycommented, Mar 25, 2021

@avendiart I test well with the same configuration with the latest extension in windows. 😅

Could you test the beta version - vscode-conventional-commits-88f5531.vsix? This version improves the log output. 😀

Confirmed, this version works well in MacOS.

Read more comments on GitHub >

github_iconTop Results From Across the Web

commitlint - Visual Studio Marketplace
Extension for Visual Studio Code - Integrate commitlint into the VS Code ... Supports all commitlint rules; Adds autocomplete support to ...
Read more >
@commitlint/config-conventional | Yarn - Package Manager
Shareable commitlint config enforcing conventional commits. conventional-changelog, commitlint ... See Conventional Commits for commit guidelines.
Read more >
Git Tutorial for Absolute Beginners from Zero to Hero - Part 15
In this video we will learn about the importance of conventions, talk about semantic versioning aka semver and conventional commits.
Read more >
How to Format Code on Save in VS Code with ESlint
If you already have the ESLint extension installed, VS Code may ... "warn" ( 1 ): violations of this rule issue a warning...
Read more >
Commitizen - GitHub Pages
If you're not working in a Commitizen-friendly repository, then git cz will work just the ... file base names relative to process.cwd() with...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found