-
Notifications
You must be signed in to change notification settings - Fork 140
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
ESlint usage incompatible with eslint.config.js
#788
Comments
I think this may be a fix: #799 I just had it only use ext if the argument is passed in. I can't tell how to test it or use it on my own repo though. |
I figured out how to use it in my repo but now I can't figure out how to make |
Also, eslint_extensions defaults to JS, so we may have a problem there. I wonder if using a version check on eslint somehow is a better solution. |
Any luck with this? It would be great to get this released since there's currently no workaround, is there? |
It seems like in #799 that using version 8.56.0 made it work for me, but 9 still does not work |
So does that mean this action doesn't support eslint v9? If not, do you guys have any recommendation that does? |
Any traction on this one ? We use this action and would like to support the v9 flows, Seems theres a PR already to add support |
This action's default usage of
--ext
when using theeslint
linter prevents the action from running when using the moderneslint.config.js
flat file configuration.This problem seems to have been highlighted by three other parties in #730, #739, and #759 but those issues were not addressed.
If there is no critical reason that this can't be updated, please keep this one open for discussion if possible. I would be happy to PR a fix for this myself if there are no major obstacles or objections.
The text was updated successfully, but these errors were encountered: