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
👋 small request here that could have saved me a bunch of time debugging. When I accidentally do module.exports.default = myConfig, the config inspector will tell me what a great config I have and how it applies loads of interesting rules to all kinds of different files. But running npx eslint (with v8.57.1) just tells me everything is ignored.
By adding lots of console.logs to eslint in my node_modules, I was able to see that one of my configs looked like { default: [...] } and that told me what to fix, but it would have been handy if the config inspector had said the config looked bad - or at least didn't tell me it was working perfectly.
The text was updated successfully, but these errors were encountered:
👋 small request here that could have saved me a bunch of time debugging. When I accidentally do
module.exports.default = myConfig
, the config inspector will tell me what a great config I have and how it applies loads of interesting rules to all kinds of different files. But runningnpx eslint
(with v8.57.1) just tells me everything is ignored.By adding lots of console.logs to eslint in my node_modules, I was able to see that one of my configs looked like
{ default: [...] }
and that told me what to fix, but it would have been handy if the config inspector had said the config looked bad - or at least didn't tell me it was working perfectly.The text was updated successfully, but these errors were encountered: