fix: update Tailwind CSS content path to use dynamic Medusa UI path#558
Open
hossam7amdy wants to merge 1 commit into
Open
fix: update Tailwind CSS content path to use dynamic Medusa UI path#558hossam7amdy wants to merge 1 commit into
hossam7amdy wants to merge 1 commit into
Conversation
|
@hossam7amdy is attempting to deploy a commit to the medusajs Team on Vercel. A member of the Team first needs to authorize it. |
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.
In pnpm monorepo setups, hard-coded paths like
./node_modules/@medusajs/ui/dist/...can break because pnpm uses acontent-addressable store and symlinks, not a flat node_modules layout.
This commit resolves the physical package location using Node’s module
resolution and constructs the Tailwind content glob dynamically.
This ensures compatibility across pnpm, npm, and yarn installs.