[Ideas] Allow for multiple versions of Forge components to 'live' inside the same environment.

Situation

ForgeComponent1 consumes ForgeComponentX version 1.0

ForgeComponent2 consumes ForgeComponentX latest version 2.0

Version 2.0 of ForgeComponentX has breaking changes (for example, a public server action is no longer available as it was in version 1.0)

Now I have the following options:

1. depend and wait on team for ForceComponent1 to make there component to use version2 of ForgeComponentX
2. clone ForgeComponent1 and do the change myself.

My preference is to minimize the need to clone forge component, for obvious reasons. But I also have project targets that I have to meet.  Both options will cost time (either I wait on the development team) or I have to spent time myself on cloning and fixing the issue myself.

Solution

Allow multiple versions of Forge components to 'live' inside the same environment.

I come from a .NET background, and the above situation has long time been tackled by Microsoft. Packages in .net are part of your solution not of the environment.

Low code should make live easier for a developer, not create old problems that I really forgot about.