Invalid index.html file transformation using global scripts in angular.json file

[fernandezn]

With what library do you have an issue?

native-federation

Reproduction of the bug/regression with instructions

When we include a global library through the project's angular.json file

Angular compiler adds the following tag:

<script src="scripts.js" defer></script>

before importing the main project file (main.js). This causes an incorrect transformation of the following tag:

<script src="main.js" type="module"></script>

Specifically, the type="module-shim" attribute is mistakenly applied to the scripts.js file tag instead of the main.js file tag. As a result, main.js file tag is left without the type="module" attribute

leading to the following error:

Expected behavior

• Tag <script src="scripts.js" defer></script> should remain untouched and should not undergo any changes
• Tag <script src="main.js" type="module"></script> should be modified to change the attribute from type="module" to type="module-shim".

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

Native Federation: v20.0.7
Angular: v20.0.6
Node: v22.13.0
Browser: Chrome v138.0.7204.97
Operating System: Windows 10

Other information

No response

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

• Yes
• No

[ladler1]

@manfredsteyer I have the same problem in version 19. The regex in updateIndexHtml.js seems to be wrong:

indexContent = indexContent.replace(/<script src="(.*?main.*?)".*?><\/script>/, '<script type="module-shim" src="$1"></script>');

see matching part in Screenshot below:

The code of version 18 worked correctly:

<script type="module" src="${polyfillsName}"></script>
<script type="module-shim" src="${mainName}"></script>`


  indexContent = indexContent.replace(
    /<script src="polyfills.*?><\/script>/,
    ''
  );
  indexContent = indexContent.replace(/<script src="main.*?><\/script>/, '');
  indexContent = indexContent.replace('</body>', `${htmlFragment}</body>`);

[mufidJab]

Also I have the same problem

[JeroenBoesten]

We also have the same issue which is currently blocking progress on our micro frontend setup.

[JeroenBoesten]

For us pinning to version 19.0.9 atleast gives us something to work with for now;
#849 (comment)