- What Laravel versions does `raulfraile/ladybug-installer` support?
- This package was designed for Laravel 3/4 and lacks modern Laravel (v5+) compatibility. It relies on Composer’s legacy PSR-0 autoloading and assumes no Laravel-specific features like service providers or facades. Use only in legacy projects or with heavy isolation.
- Will this work with PHP 8.1+ or Laravel 10?
- No, the package is incompatible with PHP 8.1+ due to its 2013 release date and likely reliance on deprecated PHP 5.x features. Laravel 10 uses PSR-4 autoloading and modern container patterns, which this installer does not support. Sandbox testing is required for older stacks.
- How do I install this package in a Laravel project?
- Run `composer require raulfraile/ladybug-installer`—it’s a Composer installer, not a Laravel service provider. However, ensure your project uses PHP ≤5.6 and Laravel ≤4.x. Modern Laravel projects should avoid this due to autoloading conflicts and missing Laravel-specific metadata.
- What happens if I use this in a modern Laravel app?
- Expect autoloading errors, namespace collisions, or broken addon installations. The package hardcodes paths like `/vendor/raulfraile/ladybug-themes` and assumes PSR-0 autoloading, which conflicts with Laravel’s PSR-4. Test in isolation or use a legacy PHP container if absolutely necessary.
- Are there modern alternatives for Ladybug addons?
- Yes. For Laravel debugging, use built-in tools like `dd()`, `dump()`, or packages like `spatie/laravel-debugbar`. For custom addons, replace this installer with a `post-install-cmd` script in your `composer.json` or use `spatie/laravel-package-tools` for modern Laravel package development.
- Does this package support Ladybug themes/plugins from other developers?
- It installs addons labeled as `ladybug-theme` or `ladybug-plugin` into `/vendor/raulfraile/ladybug-themes` or `/vendor/raulfraile/ladybug-plugins`. However, since Ladybug itself is deprecated, most addons are likely abandoned. Verify compatibility with your specific addons before use.
- How do I avoid dependency conflicts with this package?
- Lock the package to a specific version in your `composer.json` under `repositories` and avoid global installation. Use a project-specific Composer config to isolate it. Add `php-compatibility/php-compatibility` if using PHP 7.4+ to mitigate PHP version mismatches.
- Can I use this for non-Laravel PHP projects?
- Technically yes, but it’s overkill. The package is designed for Ladybug’s legacy ecosystem and lacks modern Composer features like `config.platform.check` or `replace` constraints. For generic custom installations, use Composer’s built-in `type` or `extra` fields instead.
- What security risks does this package pose?
- The package is outdated (2013) with no recent updates, risking vulnerabilities in its dependencies (e.g., old Guzzle, Monolog). Audit dependencies manually or use a static analysis tool like `sensiolabs/security-checker`. Avoid using it in production without isolation.
- How do I test if this package works in my project?
- Create a fresh Laravel 4.x project (if available) with PHP 5.6, then install the package. Verify addons appear in `/vendor/raulfraile/ladybug-themes` or `/vendor/raulfraile/ladybug-plugins`. For modern Laravel, expect failures—this is not a drop-in solution.