After composer.json update, you can execute composer install. It won't update existing packages (because of generated composer.lock), it'll only install new ones.
What has changes since your last migration?
It's the same project in the same directory? If so, it should be there.
OK thanks so much for the help.
Stupidly, I had read that to do some other operations, that missing driver is called and I had tried to run a migration the other day to change a column name and what I completely forgot was that subsequent migrate runs are trying to still run that bad one. Once i remembered and deleted the update column name migration, my add table migration ran fine. With a project due in a few weeks, no package updates for me!!
I saw this:
To rename a column, you may use the renameColumn method on the Schema builder. Before renaming a column, be sure to add the doctrine/dbal dependency to your composer.json file:
If you using doctrine 3, downgrade to "doctrine/dbal": "^2.10.3"(I don't know does laravel updated migration tools for doctrine 3. If do, you should update laravel tools).
They renamed class and Doctrine\\DBAL\\Driver\\PDOMySql\\Driver not exists
As already said, use composer require doctrine/dbal, if for whatever reason that doesn't work, use a lower version like composer require doctrine/dbal:^2.12.1 and then run composer dumpautoload -o.
Who ever is facing this issue while having
doctrine/dbal": "3.0" aleady required:
downgrade it back to
"doctrine/dbal": "^2.10".
If you still face issues for example getting
Laravel\Passport\Bridge\AccessToken::__toString() must not throw an
exception
You should require a prev version of lcobucci/jwt. It just got auto updated to 3.4, which caused these issues for me.
Took me around 3-4 hours to track everything down to this.
Hope it helps someone else too.
In my case, it was due to the version of php that did not meet the necessary requirements for that version of the package.
So, updating to any previous version is not the solution, you have to look at the requirements of each version of the package and confirm that your project complies with them.
Before modifying a column, be sure to add the doctrine/dbal dependency to your composer.json file. The Doctrine DBAL library is used to determine the current state of the column and create the SQL queries needed to make the specified adjustments to the column: