That's me done for today. Just tested one scenario and didn't encounter errors :)

• npm create vue@latest with TS, router, pinia, ESLint and Prettier
• pnpm i
• pnpm add -D eslint@latest
• Manually changedpackage.json to"lint": "eslint . --fix",
• node ~/scratchpad/create-eslint-config/bin/create-eslint-config.js
  

  /* eslint-env node */importpathfrom'node:path'import{fileURLToPath}from'node:url'import{FlatCompat}from'@eslint/eslintrc'importpluginVuefrom'eslint-plugin-vue'importjsfrom'@eslint/js'const__filename=fileURLToPath(import.meta.url)const__dirname=path.dirname(__filename)constcompat=newFlatCompat({baseDirectory:__dirname,recommendedConfig:js.configs.recommended})exportdefault[  ...pluginVue.configs['flat/essential'],js.configs.recommended,  ...compat.extends('@vue/eslint-config-typescript'),  ...compat.extends('@vue/eslint-config-prettier/skip-formatting'),{files:[],languageOptions:{ecmaVersion:'latest'}}]

• Manually changedeslint.config.js tofiles: ['**/*.vue', '**/*.js', '**/*.jsx', '**/*.cjs', '**/*.mjs', '**/*.ts', '**/*.tsx', '**/*.cts', '**/*.mts'],
• pnpm lint --> Success 🎉

I don't know for sure that all the rules work properly, but a nice first result.

This should now be ready for review!

As for now, I'll go and test the various configs increate-vue projects and report back with some results.

Back with some results. In general, the common configs seem to work.

The only parsing error I encountered was with scenario 8, which I haven't looked into.

You can view the results in this Gist:https://gist.github.com/JoostKersjes/0e6495987a74df8ebf4527f35d924e27

Just out of curiosity, why give the option of using the deprecatedeslintrc? 🤔

Just out of curiosity, why give the option of using the deprecatedeslintrc? 🤔

Made me think for a bit, thanks. I didn't want to be too disruptive with this MR so it could be more easily reviewed, so I didn't want to remove the old code.

From my perspective, the adoption of flat configs has been slower than I expected. Most of the packages aren't compatible and only have instructions for using aneslintrc config. This didn't give me a lot of confidence.

Using packages wrapped inFlatCompat wasn't as smooth as I hoped it to be when I did the ESLint v9 migration at work. I thought that it might be nice to opt out as long as the compatibility layer is needed.

PS: It seems that only a small group of people would runnpm create @vue/eslint-config@latest themselves instead of just using whatevernpm create vue@latest gives them. If someone wants to generate a specific config file, I'd guess that more options are better.