fix: convert backslash paths to forward slashes for Tailwind v4 on Windows - #891
Merged
treoden merged 1 commit intoMar 18, 2026
Merged
Conversation
… v4 on Windows Closes evershopcommerce#890
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.
Summary
On Windows, Tailwind v4 @source directives break because
path.resolveuses backslashes, resulting in missing utility classes (likerounded-xl,shadow-xs,ring-1) from the compiled CSS.This commit converts the backslashes to forward slashes.
Problem
Closes #890
Solution
Wrapped the returned sources in
getTailwindSourceswithsources.map((s) => s.replace(/\\\\/g, '/'))ensuring that Tailwind can correctly parse and apply the paths.Testing