-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tailwind imports using path instead of package #2757
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 8c79436 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
Someone is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand your described problem, can you share more details about weird behavior
The current tailwind config for the Docs theme generates tailwind classes for nextra components that cross the package boundary. This leads to weird behavior if a user wants to modify either nextra or the docs theme without effecting the other as the css is coupled.
This PR uses the Nextra build assets instead of the source files from the Nextra package. This should make it easier for developers to build in the monorepo without unexpected css issues.