Skip to content

Add .mjs resolution to Native Federation esbuild adapter - #993

Closed
Daniel4o wants to merge 2 commits into
angular-architects:mainfrom
Daniel4o:bugfix/nf-esbuild-mjs-support
Closed

Add .mjs resolution to Native Federation esbuild adapter#993
Daniel4o wants to merge 2 commits into
angular-architects:mainfrom
Daniel4o:bugfix/nf-esbuild-mjs-support

Conversation

@Daniel4o

@Daniel4o Daniel4o commented Nov 20, 2025

Copy link
Copy Markdown

Summary

Add resolveExtensions to the NF Angular esbuild adapter so .mjs entrypoints are resolved alongside TS/JS

Context

Shared/exposed packages that publish index.mjs fail to resolve during NF builds (esbuild error: “Could not resolve …”) because .mjs isn’t in the default extensions list.

Testing

Local NF build with a shared module that exposes an index.mjs now completes without resolution errors

We want to allow ng-packagr output (.mjs) to be used in federation
@Aukevanoost

Copy link
Copy Markdown
Collaborator

@Daniel4o Hi! thanks for your PR, unfortunately this is a duplicate of #987, perhaps you can propose to add your extra extensions in that PR? to keep it structured

@Daniel4o
Daniel4o force-pushed the bugfix/nf-esbuild-mjs-support branch from e482831 to c14092d Compare November 21, 2025 11:20
@Aukevanoost

Copy link
Copy Markdown
Collaborator

Su

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants