Workspace libraries with wildcard tsconfig paths are not shared between shell and remotes (NG0912 collisions)

[maciekv]

With what library do you have an issue?

native-federation

Reproduction of the bug/regression with instructions

1. In a monorepo with shell + remote apps, create a workspace library at libs/features/ with components (e.g. SpinnerComponent, TableFiltersComponent)
2. Map it via wildcard tsconfig path:

// tsconfig.base.json
"paths": {
  "@features/*": ["libs/features/src/*"]
}

3. Use shareAll() in federation config:

const sharedDeps = shareAll({ singleton: true, strictVersion: true, requiredVersion: 'auto' });

module.exports = withNativeFederation({
  name: 'my-remote',
  exposes: { './Routes': '...' },
  shared: { ...sharedDeps },
});

4. Import feature components in both shell and remote via wildcard path:

import { SpinnerComponent } from '@features/spinner/spinner.component';

5. Serve shell + remote together: nx run-many -t serve -p shell,remote1,remote2
6. Open browser console → NG0912 warnings for every component used in both shell and remote

Root cause: normalizeSharedMappings in with-native-federation.js filters out wildcard paths:

const result = paths.filter((p) =>
  !(isInSkipList)(p.key, skip) &&
  !p.key.includes('*')  // wildcards excluded
);

Non-wildcard paths (e.g. "@admin-panel/core": ["libs/core/src/index.ts"]) are shared correctly — no collisions. Only wildcard-mapped libs are affected.

I see PR #571 addresses this — is there an ETA or a recommended workaround?

Expected behavior

Workspace libraries mapped via wildcard tsconfig paths should be shared between shell and remotes, the same way non-wildcard mapped paths are. Each component class should be loaded once at runtime, not duplicated per app.

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

@angular-architects/native-federation: 21.1.1
@softarc/native-federation: 3.5.2
Angular: 21.1.5
Node: v20.19.5
Browser: Chrome
OS: macOS Darwin 24.4.0

Other information

The monorepo has 23 remote apps + shell. The libs/features/ library contains 27 feature components imported via @features/* across 489 files. Refactoring all imports to a single barrel entry point or converting to ng-packagr secondary entry points would be significant effort. A native solution for wildcard path sharing would be ideal.

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

• Yes
• No

[Aukevanoost]

Hi @maciekv,

Yeah, I checked and you're right! This behavior is not yet implemented. I'll add it to the list.

[rainerhahnekamp]

@Aukevanoost, is this Sheriff-related?

[Aukevanoost]

Hi @rainerhahnekamp

No don't think so, this has been for a long while and is "hardcoded" disabled:

module-federation-plugin/libs/native-federation-core/src/lib/config/with-native-federation.ts

Lines 124 to 126 in 22601f7

	if (paths.find((p) => p.key.includes('*'))) {
	logger.warn('Sharing mapped paths with wildcards (*) not supported');
	}

I already fixed it for externals, so I think it's just re-implementing this but then for shared-mappings:
https://github.com/angular-architects/module-federation-plugin/pull/1013/changes

haven't tried it out though