A new format for ESLint configuration files is supported since 2022 and will be the default one in version 9. Transitioning to this new configuration file format should be done but once again when our main dependencies will export those kind of files. This is already the case for eslint-plugin-vue but not for eslint-config-standard (well it is already if you checkout the master branch on GitHub but not if you install the official NPM package).
Making the transition will force us to get rid of @vue/eslint-config-standard which is used automatically by vue-cli and first versions of create-vue. What it basically does is configure ESLint to use vue rules and standardJS ones.
Newer versions of create-vue don't use it anymore but don't include standardJS anymore neither so I think we could easily depart from @vue/eslint-config-standard but what about standardJS? Should we keep it? I personally think we should as I like this style guide but please give me your opinion on this one!
This issue is derived from #377 and the text above was initially provided by @sronveaux .
A new format for ESLint configuration files is supported since 2022 and will be the default one in version 9. Transitioning to this new configuration file format should be done but once again when our main dependencies will export those kind of files. This is already the case for
eslint-plugin-vuebut not foreslint-config-standard(well it is already if you checkout the master branch on GitHub but not if you install the official NPM package).Making the transition will force us to get rid of
@vue/eslint-config-standardwhich is used automatically byvue-cliand first versions ofcreate-vue. What it basically does is configure ESLint to usevuerules andstandardJSones.Newer versions of
create-vuedon't use it anymore but don't includestandardJSanymore neither so I think we could easily depart from@vue/eslint-config-standardbut what aboutstandardJS? Should we keep it? I personally think we should as I like this style guide but please give me your opinion on this one!This issue is derived from #377 and the text above was initially provided by @sronveaux .