Forcing remotes to use a package chunk from shell regardless of the version

[Ketec]

For which library do you need help?

native-federation

Question

How to enforce the remote to use already loaded version of a package and ignore the version difference?

In webpack version, you could preload packages - and you got a warning if there was a conflict.
But it always used the module Shell had already loaded.

Now however, i run into major issue with common libraries not getting shared anymore.

Shell has 20.0.1 and remote has 20.0.0 - it creates it's own copy of it and all the services, date, providers, etc. are uninitialized.
This is a substantial problem - keeping every module instantly up to date, with many teams is unreasonable.
More often than not, the new version is backwards compatible (a new component, new input etc).

Is there a specific config i need to enforce it/use package that is already loaded in shell? This kind of ruins the whole MFE approach entirely.
Using v20.0.7
singleton does not seem to help.

  features: {
    ignoreUnusedDeps: false
  }

In shell did not help, hoped it prevents it from just cleaning everything up.
It seems like it generates the chunks based on version number?

[Aukevanoost]

Hi @Ketec,

I'm trying to understand your issue, are you talking about a sharedMapping? That is, shared libraries in a monorepo. This broke indeed and could be resolved with ignoreUnusedDeps: false as discussed in #927.

If you're talking about npm packages not being shared, it is indeed true that currently the native-federation doesn't support sharing externals. (#844) This is in progress and is a bit tricky because of Angular's way of building , also check the discussion of #645.

Is this what you meant?

[Ketec]

Not using sharedMapping (not using monorepo so it does not do anything), the common library is a npm package installed in both shell and remotes.