@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.

Quick update on this one for my setup ... I couldn't get it to work, so went back to using the Tailwind CLI to build the output.css file. It's really not that much more effort than using postCSS.

Running ng-serve with verbose flag, It appears to loop on tsconfig.federation.json flagging it each time as "modified".

EDIT:
Ok, the problem is little bit odd:
angular-esbuild-adapter.ts:355 calls doesFileExist, which compares the old content with a possible new content:

 if (!fs.existsSync(path)) {
    return false;
  }
  const currentContent = fs.readFileSync(path, 'utf-8');
  return currentContent === content;

The problem here is that content is the result of JSON.stringify, while currentContent is just the result of fs.readFileSync.

When we try to return the comparison between currentContent and content the comparison will always be false, ending always creating a new tsconfig.federation.json

  if (!doesFileExist(tsconfigFedPath, content)) {
    fs.writeFileSync(tsconfigFedPath, JSON.stringify(tsconfig, null, 2));
  }

I think the solution here is to add a new argument/create a different function that actually check if two JSON are equal such as:

function doesFileExist(path, content, jsonCompare = false) {
    if (!fs.existsSync(path)) {
        return false;
    }
    const currentContent = fs.readFileSync(path, 'utf-8');
    if (jsonCompare) {
       // maybe inside a try/catch
        const currentJson = JSON.parse(currentContent);
        const newJson = JSON.parse(content);
        return JSON.stringify(currentJson) === JSON.stringify(newJson);
    }
    return currentContent === content;
}

and updating the if:

  if (!doesFileExist(tsconfigFedPath, content, true)) {
    fs.writeFileSync(tsconfigFedPath, JSON.stringify(tsconfig, null, 2));
  }

I'm not really confident with the library and I'm not sure my analysis it's 100% correct, let me know!

EDIT 2:

If someone wants to try it meanwhile, you can:

• Install patch-package as devDependencies
• Add "postinstall": "patch-package", as script
• In the root of your project create a patches folder.
• Create a file called @angular-architects+native-federation+19.0.16.patch inside the patches folder:

diff --git a/node_modules/@angular-architects/native-federation/src/utils/angular-esbuild-adapter.js b/node_modules/@angular-architects/native-federation/src/utils/angular-esbuild-adapter.js
index 1512337..084c3db 100644
--- a/node_modules/@angular-architects/native-federation/src/utils/angular-esbuild-adapter.js
+++ b/node_modules/@angular-architects/native-federation/src/utils/angular-esbuild-adapter.js
@@ -204,16 +204,26 @@ function createTsConfigForFederation(workspaceRoot, tsConfigPath, entryPoints) {
     }
     const content = json5_1.default.stringify(tsconfig, null, 2);
     const tsconfigFedPath = path.join(tsconfigDir, 'tsconfig.federation.json');
-    if (!doesFileExist(tsconfigFedPath, content)) {
+    if (!doesFileExist(tsconfigFedPath, content, true)) {
         fs.writeFileSync(tsconfigFedPath, JSON.stringify(tsconfig, null, 2));
     }
     tsConfigPath = tsconfigFedPath;
     return tsConfigPath;
 }
-function doesFileExist(path, content) {
+function doesFileExist(path, content, jsonCompare = false) {
     if (!fs.existsSync(path)) {
         return false;
     }
+
+    if (jsonCompare) {
+      try {
+        const currentContent = fs.readFileSync(path, 'utf-8');
+        const currentJson = JSON.parse(currentContent);
+        const newJson = JSON.parse(content);
+
+        return JSON.stringify(currentJson) === JSON.stringify(newJson);
+      } catch (e) {}
+    }
     const currentContent = fs.readFileSync(path, 'utf-8');
     return currentContent === content;
 }

• Install dependencies with your package manager

EDIT 3:
Probably is it just possible to remove json stringify passed to the doesFileExist

I have the same issue, How I can fixed. @kettei-sproutty @ratsey @smarza

Hi @yasmany-santalla , I haven’t found any solutions so far, so I ended up downgrading to Tailwind CSS 3.