I am upgrading to L5 this weekend and already have a stopper. I tried both of these in my composer.json file, neither are working upon a composer update.
"aws/aws-sdk-php-laravel": "1.*"
"aws/aws-sdk-php-laravel5": "1.*"
Error message: "Your requirements could not be resolved to an installable set of packages."
Most third-party packages won't be updated for Laravel 5 yet, and this is the case for the AWS SDK. There is a Github issue for Laravel 5 support you can follow for updates.
If you use a lot of packages, it may be a few months before everything is ported over.
Related
I am new to laravel and I am wondering how all these default templates are upgraded when a new minor(!) laravel version was released.
Let's say I've installed laravel via:
composer create-project laravel/laravel example-app
This pulls in a lot of files with basic templates to get started.
Now when I run composer outdated it shows me which versions are currently out of date. I guess that composer update will only update the vendor files, but not the files inside my project itself. But what if those template files were changed on an update? How do I get to know this change?
The same question applies to packages like sanctum, fortify and jetstream. How do I manage those updates? Or aren't the template files ever being corrected between minor versions?
I try to install martinlindhe/laravel-vue-i18n-generator with Laravel 8 and it show the error:
It says 'This repository has been archived by the owner. It is now read-only.' So it is archived and that means it won't be developed. Since Laravel 8 is never than this package (last commit was like 2 years ago for this package).
Try to look Laravel's default language solution or found this package
Try to look at vue-i18n-extract
I changed in my composer "laravel/framework": "^6.0". I ran the command composer update and I get an error and it's not updated.
My current version is 5.8.2 Thanks for the help!
Image with error:
https://imge.to/i/vUDUvy
From what I can see in the message in your screenshot, it looks like Laravel Omnipay may not yet be ready for laravel 6.0. According to the git page, it may not have been updated recently.
You may wish to check with the developer, Barryvdh, to see if there will be an upgrade coming soon.
With the release of Laravel 5.5 last week, the package filp/Whoops got revamped.
However, if you follow the official Laravel 5.5 upgrade guide, it does not mention anything about filp/Whoops.
As a result, you will still have the old filp/Whoops UI. So how do you get the new filp/Whoops version with Laravel 5.5?
OLD UI in Laravel 5.4:
New UI in Laravel 5.5:
Well, it turns out that you simply need to add it manually to your composer.json. This is undocumented in the official upgrade guide at the time of writing.
composer require filp/whoops
In fact you should look at https://github.com/laravel/laravel/blob/master/composer.json and make sure you have all the dependencies mentioned there in correct versions.
Probably when you are making such migration (from Laravel 5.4 to Laravel 5.5) you should also remove composer.lock file and vendor directory and run composer install to install latest versions of packages.
How do I upgrade from Laravel 4.2 to 5 dev?
Yes, I have read the documentation but it doesn't help. What I've done so far is updated the composer.json and then I ran composer update --no-scripts.
But the file structure seems to be the same...
Would it be easier to just do a fresh install and move files and code over manually?
Laravel 5 is not even in Beta yet.
Once it is available for use - Taylor will provide a structured upgrade process to move from 4.2 to 5.
In the meantime, you should be careful about using Laravel 5 - as the structure is changing almost daily, so Taylor does not recommend using it in projects yet.
Edit: Laravel 5 has now officially been released. Here is the official upgrade guide.