Mention in project description that XO is an ESLint wrapper #528
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.
With this PR I change the description in
readme.md
(1st phrase) and inpackage.json
, from:JavaScript/TypeScript linter with great defaults
to:JavaScript/TypeScript linter (ESLint wrapper) with great defaults
in order to better clarify/stand out that xo uses ESLint underneath, an already very popular and widely used JavaScript linter,
and that it's not a linter itself, like JSLint, JSHint, ESLint, etc,
something that might discourage a new user from trying it, if he sees it for the first time, and has never heard of it.
Currently, searching in GitHub and npmjs,
the description, as it is, and the tags used in npmjs,
might all give the wrong impression that it's the opposite:
screenshots:
GitHub search
npmjs dropdown
npmjs search
Thank you