Recommend ESLint IDE integration for lint workflow - #2843
Merged
Conversation
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
johnsimons
approved these changes
Mar 27, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Updates documentation to recommend ESLint IDE integration (Option 1) for catching lint errors during development.
Why ESLint IDE integration is recommended:
The ESLint extension provides comprehensive coverage of all lint rules directly in the editor - you see errors as red squiggles as you type, before you even save. This includes not just formatting issues (which Prettier handles) but also code quality rules, unused variables, type issues, and Vue-specific rules that Prettier doesn't cover.
Changes:
Context:
Related to #2832 - addresses feedback about lint visibility in local development after removing ESLint from vite-plugin-checker (which doesn't yet support ESLint v10).