Weave Code
Providers Laravel Package
juy/providers
Loads Laravel service providers and aliases from a dedicated config/providers.php file to keep config/app.php clean. Group providers by app, package, local (dev), and production environments, and auto-register them via a single service provider.
Laravel package to load providers and aliases use a config file.
Frequently asked questions about Providers
- How does this package help with managing Laravel service providers in large applications?
- This package moves all service providers and aliases from `config/app.php` into a dedicated `config/providers.php` file, organized by type (app, package, local, production). This keeps your main config file clean and reduces clutter, especially useful for legacy Laravel 5.x applications with many dependencies.
- Does this work with Laravel 6 or newer versions?
- No, this package only supports Laravel 5.1–5.3. Modern Laravel versions (6+) use auto-discovery, environment-specific configs, and optimized bootstrapping, making this package redundant. If upgrading, manually migrate providers to `config/app.php` or use Laravel’s built-in features.
- What PHP versions are supported by this package?
- The package requires PHP 5.5.9 or higher, but it lacks support for PHP 8.x. If you’re using PHP 8.x, this package won’t work, and you should rely on Laravel’s native provider management instead.
- Can I use this package alongside other Laravel packages that modify service providers?
- There’s a risk of conflicts, especially with packages that override provider registration (e.g., `laravel-zero` or `spatie/laravel-package-tools`). Test thoroughly after installation, as this package modifies the core bootstrapping process, which could interfere with other packages.
- Is there a way to test if providers are loading correctly after setup?
- Yes, run `php artisan config:clear` and `php artisan cache:clear` to reset cached configurations. Then, use `php artisan tinker` to check if providers are registered by running `App::runningInConsole()` or inspecting the service container with `App::make('some-bound-class')`.
- What happens if I have duplicate providers in different groups (e.g., app and package)?
- The package loads providers in a predefined order (app, package, local, production), but duplicates may cause unexpected behavior. Review your `config/providers.php` to ensure no provider is listed more than once, or use conditional logic to handle environment-specific overrides.
- Are there any security concerns with using this package?
- Since the package hasn’t been updated since 2016, it may contain unpatched vulnerabilities in its dependencies (e.g., `illuminate/support` v5.x). Avoid using it in production environments unless you’ve audited all dependencies for security risks.
- How do I remove this package if I decide it’s not suitable?
- Run `composer remove juy/providers` to uninstall the package. Then, manually migrate all providers and aliases from `config/providers.php` back to `config/app.php`. Clear caches afterward with `php artisan config:clear` and `php artisan cache:clear`.
- What are the alternatives for managing providers in Laravel 5.x?
- For Laravel 5.x, you can manually split providers into modular config files (e.g., `config/app_providers.php`) and merge them into `config/app.php`. Alternatively, use `spatie/laravel-package-tools` (v1.x) for better package management, though it’s also outdated.
- Will this package work with Laravel Forge, Vapor, or Sail?
- No, this package is designed for Laravel 5.x and doesn’t integrate with Laravel Forge, Vapor, or Sail, which rely on optimized bootstrapping and modern Laravel features. If you’re using these platforms, stick to Laravel’s native provider management.
Weaver
How can I help you explore Laravel packages today?