ESLint v9?

[JakNowy]

What is the current state and recommended convention for eslint configuration in Quasar? Recently I tried bumping esling to version 9 but it doesn't seem to be compatible with standard .eslintrc.cjs. On the other hand reverting to eslint 8 gives me a couple of npm warnings:

npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated eslint@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
npm warn deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
npm warn deprecated @humanwhocodes/config-array@0.13.0: Use @eslint/config-array instead
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported

In fact it works fine but I'm curious if there's some recommended way to address that.

[yusufkandemir]

If we let aside Quasar, upgrading from ESLint v8 to v9 isn't simple, mostly due to going from eslintrc(e.g. .eslintrc.js) to flat config (e.g. eslint.config.js). https://eslint.org/docs/latest/use/migrate-to-9.0.0
So, you need to update everything accordingly.

As for the Quasar side, if you create a new project and choose app-vite v2 or app-webpack v4, it will use ESLint v9. If you want to upgrade your existing project, you can create a new project and try to make your existing linting setup similar to it.