fix: Upgrade tailwindcss to 3.4.17 to fix Node.js 22.12+ compatibility

[benceruleanlu]

Summary

Upgrades tailwindcss from 3.4.4 to 3.4.17 to fix a critical build error that occurs with Node.js 22.12+ and 23.x:

ERROR [vite] Internal server error: [postcss] Cannot read properties of undefined (reading 'call') File: /frontend/src/assets/css/style.css:undefined:NaN at /frontend/tailwind.config.js:226:39 

Root Cause Analysis

The Bug Chain

1. Node.js 22.12 introduced native require(esm) support
   module: unflag --experimental-require-module nodejs/node#55085

   • Allows CommonJS to directly require ESM modules without experimental flag

2. Our commit 7d6e252 triggered the issue by changing:

   - import { iconCollection } from './build/customIconCollection.js' + import { iconCollection } from './build/customIconCollection.ts'

3. The exact failure path in our codebase:

   • Tailwind CSS internally calls require('./tailwind.config.js')
   • Node.js 22.12+ attempts to handle our ESM config with native require(esm)
   • Our config imports customIconCollection.ts which uses import.meta.url (ESM-only)
   • The native require fails because it can't handle TypeScript + ESM features
   • Critical: Node.js leaves poisoned/invalid entries in require.cache

4. Cache poisoning causes the actual error:

   • Tailwind falls back to jiti after the failed require
   • Jiti checks Node's require.cache and finds the poisoned entries
   • The @iconify/tailwind module is returned as {} instead of the actual module
   • Line 226: addDynamicIconSelectors({}) tries to call an empty object
   • Result: "Cannot read properties of undefined (reading 'call')"

The Fix

Tailwind CSS 3.4.17 includes a workaround that forces jiti to always handle config loading, completely bypassing Node's problematic require(esm) attempt. This prevents the cache poisoning issue entirely.

Related Issues & PRs

• Tailwind CSS Issue: Plugins no longer load when using Node 22.12.0 and 23.* tailwindlabs/tailwindcss#15374 - Original bug report for plugins not loading with Node 22.12+
• Tailwind CSS Fix: Work around issue with Node 22 and Jiti tailwindlabs/tailwindcss#15421 - Workaround to always use jiti
• Jiti Root Cause: Jiti handles imports incorrectly in Node 22.12+ after a require(esm) call fails unjs/jiti#346 - Cache poisoning bug in jiti
• Jiti Fix: fix: use native require cache of loaded entries only unjs/jiti#348 - Fix to ignore invalid cache entries

Impact

This upgrade is required for compatibility with:

• Node.js 22.12.0 and later
• Node.js 23.x

Without this fix, the build fails completely when using Tailwind plugins with these Node versions.

┆Issue is synchronized with this Notion page by Unito

[github-actions]

🎭 Playwright Test Results

✅ All tests passed across all browsers!

⏰ Completed at: 08/28/2025, 06:08:21 AM UTC

📊 Test Reports by Browser

• ✅ chromium-0.5x: View Report
• ✅ chromium-2x: View Report
• ✅ chromium: View Report
• ✅ mobile-chrome: View Report

---

🎉 Your tests are passing across all browsers!

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	semver@​7.7.2

View full report

[DrJKL]

I think I'd rather we set the minimum node version to 24, and hopefully get rid of the tailwind config with the v4 upgrade.

[DrJKL]

This should be resolved by #5246 and #5248