Endless Loop in "Building Federation Artefacts" When Using @tailwindcss/postcss with Tailwind CSS 4

[smarza]

With what library do you have an issue?

native-federation

Reproduction of the bug/regression with instructions

I'm experiencing an issue when integrating Tailwind CSS 4 with the native-federation setup. Following the official Tailwind CSS Angular guide, I upgraded to Tailwind CSS 4 and moved @tailwindcss/postcss to devDependencies (as suggested in #746).

After running ng serve [any project], any file change triggers an endless loop where the "Building federation artefacts" message is printed repeatedly, even though there are no new output file changes. This makes development very cumbersome.

Steps to Reproduce:

Clone the nf-test repository.
Install Tailwind CSS 4 following the Tailwind CSS Angular guide.
Move @tailwindcss/postcss from dependencies to devDependencies.
Run ng serve [any project].
Make any file change and observe the endless loop in the federation artifacts build process.

Expected behavior

The federation artifacts should build once (or only when necessary) rather than repeatedly triggering an endless build loop after each file change.

Versions of Native/Module Federation, Angular, Node, Browser, and operating system

@angular-architects/native-federation: ^19.0.5
Angular: ^19.0.0
Node: v22.10.0
Browser: (Issue observed during development; browser details not directly relevant)
Operating System: (Tested on your development OS – please specify if needed)

Other information

No response

I would be willing to submit a PR to fix this issue

• Yes
• No

[ratsey]

@smarza @manfredsteyer I'm seeing the same in my current work project.

I took a fork of the test Stackblitz project for a completely different issue I'm chasing and interestingly that doesn't do the loop, despite seemingly having the same settings for N-F, PrimeNG, Tailwind 4, and PostCSS. Something must be different - hopefully this repo might help expose something?

Edit: Sadly, this repo does exhibit the problem, my mistake. The difference is that it doesn't do it until something is changed. My work project does it right from the initial ng serve shell.