🪟 fix: Windows Vite Build Issue #2663
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.
Summary
Issue Encountered:
We experienced a recurring problem where the TailwindCSS classname
peer-focus
caused Vite to hang, but this issue was only manifesting on Windows 11 environments, not on Linux.Diagnosis:
Investigation suggested that the usage of
peer-focus:dark
was problematic due to potential deep recursion or complexity in CSS generation, which was not well-handled by the Windows version of Node.js or Vite.Solution Implemented:
To resolve the issue, we adjusted the order of the TailwindCSS modifiers in our project. Specifically, we changed
peer-focus:dark
todark:peer-focus
. This minor adjustment effectively bypassed the recursion issue and resolved the hanging of Vite during development and builds on Windows 11.Additional Actions:
Conclusion:
This fix not only resolves the immediate hanging issue but also improves the robustness of our development process by incorporating comprehensive OS-specific testing, ensuring consistent behavior across all supported platforms.
Change Type
Checklist