Add dependency & dependency injection

[NaysKutzu]

Scope

Extension development

Explanation

Just allow us to have dam dependency's or other things:

1. Allow us to specify in the config.yml what yarn packages shall be installed
2. Allow us to specify in the config.yml what composer packages hall be installed
3. Allow us to make libs for blueprint plugins so we can have multiple extensions target other extensions

Is there an existing issue for this?

• I have searched the existing issues before opening this issue.

[prplwtf]

• Dependencies have to be kept track of. Multiple extensions can have the same dependency, uninstalling one extension shouldn't uninstall the other extension's dependency as well.
• Dependency versions seems like something blocking this from being implemented at the moment. How would we handle an extension using v1.0 of a dependency if another extension uses v0.7.

[NaysKutzu]

1. You can use yarn resolutions in the root project to enforce a specific version for conflicting dependencies, if necessary.

2. Use Composer's "virtual packages" or aliasing to resolve conflicts.

[prplwtf]

This still requires Blueprint to keep track of dependencies, which is currently blocking this.

[NaysKutzu]

any update @prplwtf ?

[prplwtf]

@NaysKutzu Possible implementation is isolating node modules per extension.. which would massively increase the bundle size but be easier to manage.

I can't hastily implement such a feature. This requires thinking out, just like many other parts of the framework. Bad implementations are unsupported sooner for good reason.