Skip to content

Mixed-version mode with different major versions of Angular / PrimeNG #899

@fperie

Description

@fperie

For which library do you need help?

native-federation

Question

Greetings everyone,

I wanted to send this message to congratulate you on the introduction of micro front-ends in Angular—first with the module-federation library, and now with native-federation. Well done!

In my company, we are developing a large-scale enterprise application consisting of several million lines of code, made up of numerous different Angular applications.
Each development team is responsible for its own application.

As for our tech stack, we use Angular with NGRX for state management, and PrimeNG as our UI library.

With module federation, an application can expose reusable components or wizards to other teams, which are then included in the DOM of the consuming page.
However, the more applications (and thus teams) we have, the more coordination is required to perform Angular version upgrades simultaneously across all teams.

To reduce the overhead of coordinating Angular/PrimeNG upgrades across teams, would it be possible to have separate shared scopes (or “shared pools”) per major Angular version?

This would allow each application to work independently, something like this:

Image

Have you already received similar requests?
Is there a solution that addresses this need?
What can we do?

Once again, thank you for your great work.
Fabien

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions