Fix Vite serve issues #13380
Merged
Fix Vite serve issues #13380
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
thecrypticace
approved these changes
Mar 27, 2024
Contributor
|
Hopefully we'll get a fix in Vite soon and can re-enable this. |
KrisBraun
added a commit
that referenced
this pull request
Mar 27, 2024
thecrypticace
pushed a commit
that referenced
this pull request
Mar 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix Vite hanging in Remix builds by temporarily disabling use of the Vite
waitForReuestsIdle(#13291) feature. This will cause multiple Tailwind CSS generations in some requests, especially the initial one. This might be visible as a FOUC, but the builds happen so quickly it may not be noticeable. This only affects dev server mode.A second fix addresses an issue introduced in #13218 (unreleased). The
vite:css-postplugin was being double-applied in serve mode.