ecamp
chore(deps): update dependency eslint to v9
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| eslint (source) | 8.57.0 -> 9.6.0 |
Release Notes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "Published by a pub.dev verified publisher"){kind=small}
Eslint 9 uses a new configuration format by default (called "flat configuration"). So this PR would need some config changes before we can upgrade to eslint9.
For Nuxt, some further details are described here: https://eslint.nuxt.com/guide/faq#package-disambiguation https://eslint.nuxt.com/packages/module
And here is a eslint migration guide for the new config format: https://eslint.org/docs/latest/use/configure/migration-guide
Eslint 9 uses a new configuration format by default (called "flat configuration"). So this PR would need some config changes before we can upgrade to eslint9.
For Nuxt, some further details are described here: https://eslint.nuxt.com/guide/faq#package-disambiguation https://eslint.nuxt.com/packages/module
And here is a eslint migration guide for the new config format: https://eslint.org/docs/latest/use/configure/migration-guide
also stumbled on this yesterday.
The following depdencies currently block the upgrade:
- https://github.com/import-js/eslint-plugin-import/issues/2948
- https://github.com/eslint-community/eslint-utils/issues/183
- https://github.com/typescript-eslint/typescript-eslint/issues/8211 (not yet released)
Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠️ Warning: custom changes will be lost.