breautek commented on PR #47: URL: https://github.com/apache/cordova-eslint/pull/47#issuecomment-3084245516
Not sure if this will help but... I have https://github.com/totalpave/tp-eslint-plugin that I use for my workplace. It sets up eslint in a way similar to Cordova in that: 1. It installs eslint as a dependency, if you're using NPM, the eslint binary will be able to consuming packages which typically installs this as a dev dependency. 2. Eslint package controls the versions of all eslint packages, since they have multiple packages that needs to be installed and are somewhat tightly coupled so version mismatches could introduce problems. 3. Ability to share a common config set Then my packages that consumes the eslint package does something like this for their own eslint configs: ``` let commonConfig = require('@totalpave/eslint-plugin').default; module.exports = [ ...commonConfig, { languageOptions: { parserOptions: { "project": "./spec/tsconfig.json", "tsconfigRootDir": __dirname } } } ] ``` Cordova could compare with and try to mimic how totalpave does it. And Cordova doesn't really need that languageOptions extension because we don't use typescript here. `@eslint/eslintrc` shouldn't be necessary, unless if you want to read the old format. Glancing over the PR it looks like it's setup mostly the same way already. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
