-
Notifications
You must be signed in to change notification settings - Fork 1
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
Upgrade eslint to v8.x #42
Comments
Closed
This was referenced Jun 22, 2022
This was referenced Jul 18, 2022
Merged
This was referenced Aug 4, 2022
This was referenced Aug 11, 2022
This was referenced Aug 15, 2022
30 tasks
36 tasks
28 tasks
@BilalQamar95, sprint check: we're just waiting for reviews/merges, correct? |
@arbrandes Yes, these are waiting for reviews/merges |
22 tasks
44 tasks
22 tasks
This was referenced Mar 1, 2023
@BilalQamar95, are we done here? |
Yes, seems concluded. |
github-project-automation
bot
moved this from In Progress
to Done
in Maintenance (deprecated version)
May 31, 2023
github-project-automation
bot
moved this from In review
to Closed
in Frontend Working Group
May 31, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We're currently using eslint v6.x. We'd like to upgrade this to the latest stable release v8.x.
We should be able to do this without creating any new linting errors, hopefully.
Also, it's worth noting that automated updates in https://github.com/edx/eslint-config updated our version of eslint there to 7.x. These dependencies are only used in development of the eslint-config, as it declares them as peer dependencies. https://github.com/edx/frontend-build defines the actual eslint dependencies we use, which use v6.x. So, despite our config being on v7, everything else is still on v6.x and (luckily) nothing has broken. We should straighten out this situation when doing this upgrade.
PRs
Base
Components
MFEs
Enterprise
The text was updated successfully, but these errors were encountered: