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
{{ message }}
This repository has been archived by the owner on Jun 16, 2023. It is now read-only.
With the new ESLint CLIEngine update - if I have any rules in my eslintrc, the output is undefined. I have to have an empty module.exports = {} in order to produce results.
The text was updated successfully, but these errors were encountered:
Currently ctf-migrate tries to use the rules defined in the project's .eslintrc file, if present. This is causing a lot of small issues (like this one).
I'll disable this and only use eslint-config-standard. After the migration script is generated, devs can always format it with their preferred tool before checking in the code.
With the new ESLint CLIEngine update - if I have any rules in my eslintrc, the output is undefined. I have to have an empty
module.exports = {}
in order to produce results.The text was updated successfully, but these errors were encountered: