Replacing eslint with standard cli #1796
Merged
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.
Hi,
While working on one of the plugins for koa which is used in our company I needed to study some points in the
Koa
source code, during the installation of dependencies I noticeddeprecating
warnings.In the course of studying the project's dependencies I found:
eslint-plugin-node
- the plugin has not been updated for the last 4 years and for this reason a fork ofeslint-plugin-n
was created which is recommended for use;eslint-plugin-standard
- marked as deprecated and the officialstandard
website recommends using their cli utility;.eslintrc.yml
- does not have any special settings and uses only:extends: standard
why not just update eslint?
I can see several reasons why the official utility is better than the eslint custom config ( in my opinion ofc ):
With
standartd
we have only two dependecies and one of it is optional:Checklist