fix: remove conflicting inline tailwind classes from package docs#2230
fix: remove conflicting inline tailwind classes from package docs#2230iiio2 wants to merge 3 commits intonpmx-dev:mainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughThe Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 1✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |

The TOC section count (e.g. (102)) appears bold in production but normal in development due to conflicting Tailwind utility classes between inline HTML and the CSS rule.
Cause: The tag had inline font-semibold competing with .toc-content > ul > li > a's font-medium, and Tailwind's CSS ordering differs between dev and production builds.
Fix: Removed inline utility classes from the tag in render.ts, letting the existing CSS rule handle styling so font-normal on the (102) span always wins.
Now in development:
In production:
Now in Production:
https://npmxdev-git-fork-iiio2-fix-remove-conflicting-inlin-3f1bac-npmx.vercel.app/package-docs/vue/v/3.5.30