feat(app-webpack): add ESLint 10 to peerDependencies #18305
Replies: 1 comment
|
Thanks for raising this. Since this discussion was opened, Quasar has announced that Expanding the peer range and validating the Webpack integration against a new ESLint major would be new compatibility work rather than a critical fix. For an existing app-webpack project, the supported choice is therefore to remain on ESLint 9. Using For projects moving to current Quasar tooling, the recommended path is to migrate to Given that roadmap, I would treat this request as superseded by the app-webpack sunset rather than add ESLint 10 support to app-webpack. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Description
@quasar/app-webpackcurrently declares:"eslint": "^8.57.1 || ^9.0.0"ESLint 10 is released. Projects on Quasar 4 + webpack cannot upgrade without
ERESOLVE / --legacy-peer-depsMotivation
@eslint/js10,eslint-plugin-vue@10, flat config (eslint.config,js)legacy-peer-depsin CIEnvironment
@quasar/app-webpack: 4.4.5quasar: 2.19.xeslint: 9.39.x (blocked from 10)@eslint/js:9.xeslint-plugin-vue: 10.xeslint.config.js) +eslint-webpack-pluginCurrent behavior
npm intsall eslint@10 @eslint/js@10Fails with peer dependency conflict:
peerOptional eslint@"^8.57.1 || ^9.0.0 || ^10.0.0"quasar dev/quasar build/ eslint-webpack-plugin integration work with eslint 10.Proposed solution
peerDependency.eslintto include^10.0.0eslint-webpack-plugin+ flat config with eslint 10 in a sample webpack appWorkaround (today)
npm intall -legacy-peer-depsNot ideal for CI reproducibility.
Willing to contribute
Happy to open a PR if maintainers confirm approach (peer bump + CI test.)
All reactions