-
-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Composer Warnings when installing pest-plugin-laravel #481
Comments
@eleftrik I came across the same warning and adding the Laravel framework lib to the
I installed spatie/laravel-queueable-action which also requires the Laravel Illuminate library, but Zero already installs a mirrored Illuminate library. The warning is that they're both using the same namespaces and Composer complains about it when generating the autoloader. Ideally it would be best to not install the duplicate library at all, but I'm not sure if that is possible from the Composer file? Although, are you sure you need the Laravel plugins package? Just out of curiosity, what does that plugin lib have that Zero doesn't already come pre-packaged? |
Yeah, this happens because it installs I don't think there's actually much reason to add the Laravel plugin for Pest within a Laravel Zero application. I think either we need a separate Laravel Zero Pest plugin, or you'll need to develop without the helper functions that plugin provides (which really isn't that much). |
@owenvoke I need the Laravel plugin because I'm used to its helpers. Of course, I can live without it, but it's a comfort :) |
Bran new Laravel Zero app.
I try to add
pest-plugin-laravel
:I got a lot of messages like this:
I got same warnings on each
composer dump-autoload
.Despite these warnings, I can use the plugin (for example,
artisan
helper inside a test is working).Is there a way to avoid these warnings? Am I doing anything wrong?
Thank you!
The text was updated successfully, but these errors were encountered: