Bug: UI doesn't run locally after Vite major update

[cdprete]

Hello.

I tried to run the UI locally today, because I wanted to test #5307 (comment) 😅, but it seems like that after the update done in #5170 it's not possible anymore since it fails with:

The commit before (a884cfd) works fine.

NodeJS version: 26.0.0 (originally) and 26.1.0 (after my package manager updated it)

[SteKoe]

Hi,

what did you run to get to this point? When I run npm run build the resulting bundle does not contain postcss. Have you removed node_modules or run npm ci to do so?

[cdprete]

Hi. I've run `npm run build:watch`. I dropped both the node modules and the package-lock.json and downloaded again all the dependencies, but with no luck. Il sab 9 mag 2026, 00:29 Stephan Köninger ***@***.***> ha scritto:

…

*SteKoe* left a comment (codecentric/spring-boot-admin#5345) <#5345 (comment)> Hi, what did you run to get to this point? When I run npm run build the resulting bundle does not contain postcss. Have you removed node_modules or run npm ci to do so? — Reply to this email directly, view it on GitHub <#5345 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACAZGWGHDIB3ISKCRV56PUT4ZZNVZAVCNFSM6AAAAACYWOWORSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMJQGMZDKMJXGY> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[cdprete]

I just tried the normal build (npm run build) and it works.
So, only the development mode fails.

[cdprete]

Hi @SteKoe.

Why is postcss needed to begin with?
To my understanding of the installation instructions of tailwindcss, it's not needed anymore with version 4.x when targeting vite (https://tailwindcss.com/docs/installation/using-vite) which was, instead, the case with version 3.x if not using the custom CLI.
Is this maybe some sort of missed migration from 3.x to 4.x or is indeed there a use case behind it I'm not aware of?

[SteKoe]

You are right and we got rid of postcss when migrating from tailwindcss 3 to 4, that's why i am wondering what's the issue here.

npm ls postcss prints the following for me:

spring-boot-admin-server-ui@ /Users/stekoe/workspaces/cc/spring-boot-admin/spring-boot-admin-server-ui
├─┬ @testing-library/vue@8.1.0
│ └─┬ @vue/compiler-sfc@3.5.34
│   └── postcss@8.5.14 deduped
├─┬ sanitize-html@2.17.3
│ └── postcss@8.5.14
└─┬ vite@8.0.11
  └── postcss@8.5.14 deduped

Which indicates: no postcss used in any lib that is bundled into frontend. What does it print for your setup?

[cdprete]

I'll check that tomorrow.

Nevertheless, I remember that the stacktrace in the console (the screenshot above) was pointing to sanitize-html which you also have in there.

[SteKoe]

Removing setting NODE_ENV=development solves the issue. Hence, I am going to drop it.

This is mainly caused by sanitize-html being dependant on postcss which itself is not safe to be included in browser environment, obviously.

[cdprete]

Fine for me, of course, as soon it works :)