chore(misc): migrate tailwind v3 to v4

[jaysoo]

Current Behavior

graph apps and nx-dev pin tailwindcss 3.4.4 with JS configs and v3 directives.

Expected Behavior

tailwindcss 4.1.11 via @tailwindcss/postcss. JS configs replaced with CSS-based @import 'tailwindcss', @plugin, @source, @custom-variant. astro-docs already on v4.

v3 utility renames applied across graph + nx-dev sources (per the Tailwind v4 upgrade guide) so visuals don't shift:

• shadow-sm -> shadow-xs, shadow -> shadow-sm
• drop-shadow-sm -> drop-shadow-xs, drop-shadow -> drop-shadow-sm
• rounded-sm -> rounded-xs, rounded -> rounded-sm
• blur-sm -> blur-xs, blur -> blur-sm
• backdrop-blur-sm -> backdrop-blur-xs, backdrop-blur -> backdrop-blur-sm

v3 default border-color (gray-200) preserved via @layer base compat shim per the upgrade guide's default border color note, since explicit border-color isn't always paired in existing markup.

Related Issue(s)

NXC-4430

[netlify]

✅ Deploy Preview for nx-docs ready!

Name	Link
🔨 Latest commit	6f5eb98
🔍 Latest deploy log	https://app.netlify.com/projects/nx-docs/deploys/69fb9e6ddb94400008e39a6d
😎 Deploy Preview	https://deploy-preview-35594--nx-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[netlify]

✅ Deploy Preview for nx-dev ready!

Name	Link
🔨 Latest commit	6f5eb98
🔍 Latest deploy log	https://app.netlify.com/projects/nx-dev/deploys/69fb9e6deb2b120008eba193
😎 Deploy Preview	https://deploy-preview-35594--nx-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 6f5eb98

Command	Status	Duration	Result
nx affected --targets=lint,test,build,e2e,e2e-c...	✅ Succeeded	21m 4s	View ↗
nx run-many -t check-imports check-lock-files c...	✅ Succeeded	4s	View ↗
nx-cloud record -- pnpm nx-cloud conformance:check	✅ Succeeded	16s	View ↗
nx build workspace-plugin	✅ Succeeded	<1s	View ↗
nx-cloud record -- nx sync:check	✅ Succeeded	21s	View ↗
nx-cloud record -- nx format:check	✅ Succeeded	7s	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-05-06 21:55:41 UTC

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​types/​js-yaml@​4.0.9
	npm/​picocolors@​1.1.1
	npm/​@​types/​hast@​3.0.4
	npm/​is-windows@​1.0.2
	npm/​shiki@​4.0.2
	npm/​source-map-js@​1.2.1
	npm/​cli-cursor@​3.1.0
	npm/​resolve.exports@​2.0.3
	npm/​npm-run-path@​4.0.1
	npm/​clsx@​2.1.1
	npm/​deepmerge@​4.3.1
	npm/​figures@​3.2.0
	npm/​fast-glob@​3.3.3
	npm/​import-fresh@​3.3.1
	npm/​js-tokens@​4.0.0
	npm/​ignore@​7.0.5
	npm/​string-width@​4.2.3
	npm/​open@​8.4.2
	npm/​js-yaml@​4.1.0
	npm/​cliui@​8.0.1
	npm/​convert-source-map@​2.0.0
	npm/​ansi-colors@​4.1.3
	npm/​chalk@​4.1.2
	npm/​loader-utils@​3.3.1
	npm/​rxjs@​7.8.2
	npm/​semver@​7.7.2
	npm/​semver@​7.7.4
	npm/​minimatch@​10.2.5
	npm/​ajv@​8.17.1
	npm/​picomatch@​4.0.4
	npm/​tar-stream@​2.2.0
	npm/​enhanced-resolve@​5.18.2

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: pnpm-lock.yaml → npm/entities@4.5.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@4.5.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: pnpm-lock.yaml → npm/entities@6.0.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@6.0.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[nx-cloud]

Important

At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.

Nx Cloud has identified a possible root cause for your failed CI:

We classified this failure as an environment/pre-existing issue rather than a code change because the failing e2e-gradle test encounters Kotlin compilation errors (Unresolved reference 'LinkedList') in fixture template files that were not touched by this PR. Our diff contains only Tailwind CSS configs, PostCSS configs, and TSX class-name updates — none of which could cause Kotlin's compiler to fail resolving standard library references in Gradle e2e templates.

No code changes were suggested for this issue.

Trigger a rerun:

View detailed reasoning on Nx Cloud ↗

🔔 Heads up, your workspace has pending recommendations ↗ to auto-apply fixes for similar failures.

_{🎓 Learn more about Self-Healing CI on nx.dev}