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
It still seems like there's no workaround for cosmiconfig file linting, or perhaps our usage is wrong.
For example, .xo-config.js is not linted, nor is .remarkrc.js and .pug-lintrc.js.
We've tried adding extensions: [''] and extensions: ['.xo-config.js'] even as a test to the XO config, but it still isn't linting those files. Not all config files support non-dotfile naming conventions, which makes this impossible to lint. We've also tried checking --print-config output too, and nothing seems to fix it.
Curious if you have a workaround @sindresorhus? And if so, what is it so we can document it?
The text was updated successfully, but these errors were encountered:
It still seems like there's no workaround for cosmiconfig file linting, or perhaps our usage is wrong.
For example,
.xo-config.js
is not linted, nor is.remarkrc.js
and.pug-lintrc.js
.We've tried adding
extensions: ['']
andextensions: ['.xo-config.js']
even as a test to the XO config, but it still isn't linting those files. Not all config files support non-dotfile naming conventions, which makes this impossible to lint. We've also tried checking--print-config
output too, and nothing seems to fix it.Curious if you have a workaround @sindresorhus? And if so, what is it so we can document it?
The text was updated successfully, but these errors were encountered: