When developing a custom Laravel package, you may need to require a separate package to provide functionality.
Composer makes it easy to include packages as a dependency. This is a good thing as it makes code more maintainable and means to don’t have to re-invent the wheel.
You also need to bind the third-party package to the Laravel app - you shouldn’t do this manually, as it would make using your package unecessarily complicated. Fortunately, Laravel makes it easy for you to register packages from within your custom package’s service provider class.
Use Composer to Bundle Dependencies
In this example, we’ll add the “illuminate/support” and “laravelcollective/html” packages. In your custom package
When you run
composer update at the app level, Composer is smart enough to connect the dots and add the required packages to the app
boot() method of the custom packages service provider, you can register (bind) the “laravelcollective/html” service provider. You can also load up an alias for the package:
You could simplify the alias loading by passing in an array of alias => classname values to the
This method acceps an array and merges this with the registered aliases.
comments powered by Disqus