apf_portal/apps/portal-shell/.postcssrc.json at bb9654cc32be49d209a9c1d4979b5fe8e778bad1 - apf_portal - AdAstra Git

julien/apf_portal

Files

T

Julien Gautier bb9654cc32

CI / commits (pull_request) Successful in 1m25s

Details

CI / check (pull_request) Successful in 1m35s

Details

CI / scan (pull_request) Successful in 1m35s

Details

CI / a11y (pull_request) Successful in 1m51s

Details

CI / perf (pull_request) Successful in 3m51s

Details

fix(portal-shell): use .postcssrc.json so tailwind utilities are emitted

The portal-shell scaffold shipped a `postcss.config.js`, but
`@angular/build` (Angular 17+ esbuild pipeline) does not load that
file format — it only picks up `.postcssrc.json`. Result: the
`@tailwindcss/postcss` plugin was never registered, Tailwind ran
with no source files visible, generated only its `@theme` block,
and dropped every utility class on the floor. The page rendered
unstyled — black text on white — even though `nx build` reported
success and shipped a 23 KB styles.css.

Fix: rename / re-encode the config to `.postcssrc.json`. Same
plugin, same options, just the file format Angular's esbuild
adapter actually reads.

Verified locally:
- Before:  ZERO class selectors in dist/.../styles*.css.
- After:  75 selectors in production build, including the ones
  referenced from header/footer/home/accessibility templates
  (`.text-3xl`, `.bg-amber-50`, `.font-semibold`, etc.).

The repo-layout walkthrough in `docs/development.md` is updated to
reflect the new file name and explicitly call out the gotcha so a
future contributor doesn't reach for `postcss.config.js` again.

2026-05-10 02:53:58 +02:00

6 lines

54 B

JSON

Raw Blame History

 {
   "plugins": {
     "@tailwindcss/postcss": {}
   }
 }