Upgrade eslint-config-prettier to version 7.0.0 #359
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.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ eslint-config-prettier (^6.0.0 → ^7.0.0) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by 22 commits:
eslint-config-prettier v7.0.0
Merge pull request #168 from prettier/next
Various cleanups
Fix local eslint require
Make error message fit better for eslint-plugin-prettier
Don’t warn about eslint-plugin-prettier rules if prettier/prettier is off
Remove docs moved to eslint-plugin-prettier
Reduce npm package size by 75%
Move eslint-plugin-prettier to its own file like all other plugins
Turn no-tabs into a validatable rule
Use ESLint API instead of --print-config and stdin
Use object spread instead of Object.assign
Require ESLint 7
Change "master" to "main" in GitHub Actions workflows
Merge pull request #167 from prettier/improvements
Ignore line ending differences in tests (Windows)
Make tests independent of cwd
Make it easier to debug test-lint/ errors
Use native child_process.spawnSync instead of cross-spawn in tests
Improve Github Actions
Update npm packages
Update copyright years
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands