laravel-breadcrumbs | Adds breadcrumb support to your Laravel applications

Since I didn't get any help , so I started scanning each line of code and found that there is some issue with line laravel/framework": "5.3.*" , I changed it to 5.* and ran composer install, it worked like a charm and yes it installed Laravel 5.3.8 version

the maddhatter/laravel-fullcalendar dependency need the version 5 of illuminate/support.

So you can't update laravel with this dependency. Moreover, it seems that this project was not updated since 3 years

But a fork exist here.And it works with laravel for 5,6 and 7 https://github.com/nelkasovic/laravel-full-calendar/blob/master/composer.json#L15

The package spatie/laravel-image-optimizer required the spatie/browsershot and you should`t require this separately. You can do:

laravel-link-checker package (which is, by the way, abandoned) requires laravel framework 5.6/5.7 (as you can see in its packagist page. You have Laravel 5.8 and that is not satisfiable.

You can take the sources of laravel-link-checker and re-package it but it's not guaranteed it will work for Laravel 5.8.

Your error message suggests that peridot-php/peridot package v1.16 that you require only works with symfony/console in version ~2.0, which is equivalent to any 2.x version and thus incompatible with 3.x version of symfony/console which Laravel requires.

First version of peridot-php/peridot that supports symfony/console 3.x is 1.18.1, so you need to bump your dependency to that version to support Symfony Console 3.x properly.

Thanks to @kerbholz for the solution. Moved the code below in my composer.json

After three days of racking my brain, I figured out my dumb mistake and thought I'd share.

My situation was this:

1. I had previously committed the vendor folder to my repo because I was deploying from my repo without a build step.
2. I now have a deployment pipeline set up that compiles and deploys my code when I commit to specific branches.
3. I have composer update as a command within that pipeline, so decided it was time to follow best practices and add /vendor to my .gitignore file.
4. I did not delete the /vendor folder from my repo before adding it to my .gitignore file.
5. This resulted in the /vendor folder getting locked into my repo, and not deleted from it.

I had taken all kinds of actions trying to figure out what was going on with no luck. I tried downloading the version that was on the server onto my local machine, and ran into the same problem.

TL;DR:

Finally, I stumbled across something that recommended to simply delete the /vendor folder, and then run composer install to refresh the whole vendor folder. That did the trick for me anyway. It seems like the error message for this particular problem isn't very guiding, but that's probably because no one expected anyone to be so dumb as to completely disregard the guidance of "don't commit the/vendor folder to your repo". So it seemed to be stemming from a dependency mismatch that wasn't getting resolved on composer update for my scenario.

You can see about it in https://hub.docker.com/_/adminer/

Example

You could create a component to handle the if case you are going to need: