Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates ESLint 8.57.0.
All plugins are also updated and some which were referenced inside
package.json
but are now included as dependencies of other packages were removed to keep direct dependencies list as clean as possible.This PR is also the opportunity to write some comments about ESLint future updates so everyone is aware of it :
Since V8.53, ESLint team decided to deprecate all formatting rules. More info can be found on this official announcement.
To keep it simple, those rules will stay at least in version 9 of ESLint but will not receive any updates anymore. Those rules should be abandoned in favor of a code formatter OR replaced by the rules defined in
[@stylistic/eslint-plugin-js](https://eslint.style/packages/js)
. This package contains all the deprecated rules and will be maintained. However, as our main dependencies (eslint-plugin-vue
andeslint-config-standard
) don't make use of those rules yet, it is better to wait before making the transition on our side...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 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-standard
which is used automatically byvue-cli
and first versions ofcreate-vue
. What it basically does is configure ESLint to usevue
rules andstandardJS
ones.Newer versions of
create-vue
don't use it anymore but don't includestandardJS
anymore neither so I think we could easily depart from@vue/eslint-config-standard
but 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!Last point, it is still unsure whether ESLint V9 is compatible with
Vue-CLI
so perhaps all those thoughts will only be of interest whenWegue
will be upgraded toVue3
...