feat: switch to stylish formatter for eslint #6748
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
`eslint-formatter-codeframe` is no longer provided by eslint v8, and must be isntalled separately. As the dependency is not actively maintained, we switch the default formatter to the built-in `stylish` one. See https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0#removed-formatters Refs vuejs#6740
haoqunjiang approved these changes Oct 13, 2021
| Thanks for your work on this! |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
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.
eslint-formatter-codeframeis no longer provided by eslint v8, and must be isntalled separately.As the dependency is not actively maintained, we switch the default formatter to the built-in
stylishone.See https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0#removed-formatters
Refs #6740
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
Other information: