No 3rd-party dependencies
Last updated
Was this helpful?
Last updated
Was this helpful?
The framework itself doesn't have any 3rd-party dependencies. Our do -- but we don't force you to use the same libraries we do.
For example, we are strong advocates for and we really like , but you are free to build your plugins using either no dependency injection at all or using a different container. Whenever the framework references dependency injection, it simply assumes that it's been passed on a -compatible container (which should be most, if not all, popular containers) and it always provides a fallback in case no container is used at all.
That being said, the framework does have internal dependencies. It is possible to build a plugin using only the . If you need the , it will auto-install the Bootstrapper Module as well when using since that is listed as a dependency. Similarly, the depends on both the Bootstrapper and the Helpers modules, and so on.
There is an exception though. The does NOT depend on the as it is technically an extension to the . As the depends on the Settings one, it doesn't require the Core module either.