New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
expiring-todo-comments
breaks eslint --print-config
in dirs with no package.json
#373
Comments
eslint --print-config
fails in dirs with no package.json
expiring-todo-comments
breaks eslint --print-config
in dirs with no package.json
expiring-todo-comments
breaks eslint --print-config
in dirs with no package.json
expiring-todo-comments
breaks eslint --print-config
in dirs with no package.json
@lubien, you are probably most familiar with this rule. Any thoughts? |
It might happen because one of my The solution would possibly try-catch for it, I can tackle this tomorrow if you're okay with it. |
Awesome, thanks. |
@garyking could you provide some steps to reproduce it? Just did a fresh install of this rule and ran eslint --print-config src/index.js
|
Oh damn, it must be because I'm using eslint v5, rather than the latest v6. I can't upgrade that yet, unfortunately. I'd appreciate it if you could fix this for eslint v5, since I and a lot of people are still using it, due to the major changes needed for some to upgrade to eslint v6. But I can understand if you won't fix the plugin just for eslint v5. |
Would one simple fix be to replace |
I'm on it!
I'll check it out |
If
eslint --print-config
is run in a dir with nopackage.json
, then theexpiring-todo-comments
rule throws an error. So the--print-config
command doesn't work with this rule, at the moment.The text was updated successfully, but these errors were encountered: