Skip to content

Conversation

@RobinMalfait
Copy link
Member

@RobinMalfait RobinMalfait commented Nov 7, 2024

This ensures our glob hoisting mechanism (see #14896) works on Windows when performing an upgrade.

@RobinMalfait RobinMalfait force-pushed the fix/windows-paths-when-hoisting-globs branch from 2b87abe to 7df84f0 Compare November 7, 2024 16:00
Glob patterns should be in POSIX style, so let's make sure that globs
like `../` are handled correctly.
If the incoming absolute path is already absolute, then we don't need to
try and resolve it again.
In v3 you can configure `content` to be relative to the
`tailwind.config.js` file instead of relative to the current working
directory of the process.

This ensures that the base is set correctly to the correct base instead.
@RobinMalfait RobinMalfait force-pushed the fix/windows-paths-when-hoisting-globs branch from 7df84f0 to bab0e72 Compare November 7, 2024 16:18
@thecrypticace thecrypticace marked this pull request as ready for review November 7, 2024 20:13
@thecrypticace thecrypticace requested a review from a team as a code owner November 7, 2024 20:13
@thecrypticace thecrypticace enabled auto-merge (squash) November 7, 2024 20:15
thecrypticace and others added 2 commits November 7, 2024 15:15
No need to normalize the static part because it should already be in
POSIX style.
@thecrypticace thecrypticace merged commit 99c4c04 into next Nov 7, 2024
1 check passed
@thecrypticace thecrypticace deleted the fix/windows-paths-when-hoisting-globs branch November 7, 2024 20:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants