Integrate tsc with ViteJS
#876
Open
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
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Replace vite-plugin-eslint by vite-plugin-checker to have both
eslintandtscinto the build pipeline ofvite.During dev, it show a little hover in bottom left corner, clickable to show the error output, and show in the console. So it don't block the view like before.
Also the initial runs of ESLint and Typescript are in parallel of the initial build, so no more delay for the build.
Note
Another reason of this change is because of how the actual plugin include eslint into the vite process create out-of-memory problems when trying to add Babel plugins.