Add @tailwindcss/turbopack loader - #20367
Conversation
Confidence Score: 5/5The PR appears safe to merge, although the previously requested Turbopack integration coverage is still not executed by CI. The instrumentation-label issue is fixed across the loader’s runtime paths. The new fixture exercises real initial generation and watch updates, but the integration workflow matrix does not select the turbopack directory, leaving that non-blocking coverage gap outstanding. Reviews (3): Last reviewed commit: "Use default Turbopack mode in integratio..." | Re-trigger Greptile |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
WalkthroughAdds the 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
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 |
There was a problem hiding this comment.
Actionable comments posted: 3
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 5d970c0e-53be-484b-866c-fd1ee361313d
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (8)
CHANGELOG.mdintegrations/utils.tspackages/@tailwindcss-turbopack/README.mdpackages/@tailwindcss-turbopack/package.jsonpackages/@tailwindcss-turbopack/src/index.ctspackages/@tailwindcss-turbopack/src/index.tspackages/@tailwindcss-turbopack/tsconfig.jsonpackages/@tailwindcss-turbopack/tsup.config.ts
Summary
Test plan