'Laravel PackageManifest.php: Undefined index: name

I'm just trying to deploy my application and I just ran composer update on my server and I got the following error:

In PackageManifest.php line 122: Undefined index: name

How can I fix this issue?

php laravel

Solution 1:^[1]

As a temporary fix, try this, it worked for me, in the following file:

vendor/laravel/framework/src/Illuminate/Foundation/PackageManifest.php

Find line 116 and comment it:

$packages = json_decode($this->files->get($path), true);

Add two new lines after the above commented line:

$installed = json_decode($this->files->get($path), true);
$packages = $installed['packages'] ?? $installed;

Solution 2:^[2]

I had the same problem, I just execute the command:

composer update

this will updated the composer.lock file. After that worked like a charm.

Solution 3:^[3]

I found this issue on the composer GitHub repo that helped a lot

I updated my Laravel framework from 5.8 to 5.8.38, following the table displayed in that issue and the error disappeared.

This Laravel blog post also helps

If you can't upgrade Laravel, you can just stay with Composer 1 by running

composer self-update --1

Solution 4:^[4]

I had the same problem. In my case downgrading the composer version fixed the problem. They updated Composer 4 times within 2 days - I think they had a problem with their newest updates. In my case version 1.10.1 was the version to go with.

I hope it'll work.

Solution 5:^[5]

I recently switched composer 2.0.8 and my Laravel version is 6.20.27

To solve this issue:

Step 1:

Delete compose.lock File

Step 2:

Install dependencies.

composer install

Solution 6:^[6]

I had a problem like this, and also tried composer self-update --stable, but there was no result. So, I found that this file belongs to the Laravel framework. So the following command resolved this issue:

$ composer update laravel/framework

Solution 7:^[7]

In my case downgrading the composer version fixed the problem.

sudo composer self-update --1

Solution 8:^[8]

https://github.com/composer/composer/issues/9340#issuecomment-716210369

As stated in here, your laravel version may conflict with composer 2

composer update laravel/framework

should fix your problem :D

Solution 9:^[9]

Running the following command worked for me. Maybe this will help someone needy.

composer update

Solution 10:^[10]

I removed my vendor folder and composer.lock and ran composer install again. This solved it for me.

Solution 11:^[11]

I was facing the same issue. I Saw my Laravel framework version is "laravel/framework": "6.0" So just put the cap before the version and it starts working fine. "laravel/framework": "^6.0"

Solution 12:^[12]

Running composer update worked for my project with Laravel 5.7

Solution 13:^[13]

The easiest way to solve this issue is

delete composer.lock file from your project.

Run composer install

Solution 14:^[14]

For my Laravel 5.7 project deleting vendor folder and composer.lock file fixed the issue.

Solution 15:^[15]

Some versions of composer give this error, the version 1.10.20 doesn't throw this error

composer self-update 1.10.20
composer install

Solution 16:^[16]

I have a solution:

Delete the vendor folder.
run composer install

Don't use --no-scripts. This will cause a problem, and will not create the appropiate folders which the file PackageManifest.php and others need.

run composer update

This is so you don't have problems with bugs in the file.

Solution 17:^[17]

Try this, it is worked for me, in the following file:

vendor/laravel/framework/src/Illuminate/Foundation/PackageManifest.php

Find this line and comment on it

$packages = json_decode($this->files->get($path), true);

Add two new lines after the above-commented line

$installed = json_decode($this->files->get($path), true);
$packages = $installed['packages'] ?? $installed;

Solution 18:^[18]

If you want to fix without making updates and composer updates

just go to vendor/composer and remove installed.json

Solution 19:^[19]

Running the following command fixed it for us

composer self-update --stable

Solution 20:^[20]

To downgrade composer to an old version:

composer self-update <version>

Example:

composer self-update 1.10.1

Solution 21:^[21]

here's a solution that worked for me. https://github.com/composer/composer/issues/9340#issuecomment-716210369 change your laravel framework to 6.18.7 so that its compatible with composer 2

Solution 22:^[22]

No need to force an upgrade on your packages (running composer update on production is not recommended anyway) or downgrade your Composer if it's on version 2.

If you have a website that requires Composer v1 for updates (because, for example, v2 causes errors) and you have version v2 installed globally, the quickest solution is:

Step 1

Download the latest stable 1.x composer.phar from https://getcomposer.org/download/ (under Manual Download).

Step 2

Place the downloaded composer.phar file in the root of your project (where the composer.json file resides).

Step 3

Run your command using the composer.phar file. Example:

php composer.phar install

Solution 23:^[23]

I had the same problem after i clone an laravel project and start composer install. Then I read through some solutions here. In my opinion, it is not a good idea to edit the laravel core. But if it's just for testing, why not.

My solution in my case was composer update instead composer install. In the case of composer update, it does not use the composer.lock file and updates the packages from composer.json. For me and in my special case works.

Solution 24:^[24]

On my computer composer version 2.0.9 was installed, I had the same problem when upgrade laravel project.

the solution is :

Delete Vendor folder inside your project if exist.
inside composer.json for laravel version write this "laravel/framework": "^6.0" don't forget ^ in front of 6.0 it needs to install latest version of laravel 6
then composer update

finally, it works perfectly.

Solution 25:^[25]

I updated to Composer 2.0.11 and I had the error. Downgraded to Composer 1.10.20, it worked great, BUT IT'S VERY VERY SLOW.

So for those like me who don't want to change the vendor code, and still want Composer 2.0.x know that it was a kind of bug in Laravel, and Laravel has fixed it in minor versions (or hotfixes). I was using Laravel 5.7.9 and my vendor/laravel/framework/src/Illuminate/Foundation/PackageManifest.php ->build() was like:

if ($this->files->exists($path = $this->vendorPath.'/composer/installed.json')) {
    $packages = json_decode($this->files->get($path), true);
}

But in Laravel 5.7.29 PackageManifest.php , the same file is fixed:

if ($this->files->exists($path = $this->vendorPath.'/composer/installed.json')) {
    $installed = json_decode($this->files->get($path), true);

    $packages = $installed['packages'] ?? $installed;
}

Same goes for Laravel 5.6.0 that had the bug, and is fixed in 5.6.40 Laravel 5.6.40 PackageManifest.php. I don't know from which minor version it has been fixed at each level, but I suggest to go for the last, like 5.7.29, 5.6.40 etc. Or you can go look the versions to see if it has been fixed.

NOW COMPOSER 2.0 IS VERY VERY FAST.

Solution 26:^[26]

If the error is after self updating the composer, just replace composer with composer1.
Just change:

composer install ...

into:

composer1 install ...

Just this!

Solution 27:^[27]

If you have composer version 2 upgrade your laravel to 6.2.

https://github.com/composer/composer/issues/9340#issuecomment-716210369

Solution 28:^[28]

run a composer upgrade. This work for me on laravel 7

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution	Source
Solution 1	Jon Winstanley
Solution 2	Will Bin Lopes Cordeiro
Solution 3	Salim
Solution 4	guyaloni
Solution 5	Bedram Tamang
Solution 6	DavidHyogo
Solution 7	Gerardo Argueta
Solution 8	truongnm
Solution 9	Satendra Rawat
Solution 10	Jos Koomen
Solution 11	Abrar Ahmad
Solution 12	Joundill
Solution 13	Sk Shoyeb
Solution 14	Nabil
Solution 15
Solution 16	SherylHohman
Solution 17	Chinthaka Dilan
Solution 18	Burhan Ibrahimi
Solution 19	Nick Zinger
Solution 20	Prograymer
Solution 21	user7657700
Solution 22	ChimeraTheory
Solution 23	Maik Lowrey
Solution 24	Lan Danel
Solution 25	KeitelDOG
Solution 26	Mohsen Abasi
Solution 27	Webkix
Solution 28	Gheorghe

'Laravel PackageManifest.php: Undefined index: name

Solution 1:[1]

Solution 2:[2]

Solution 3:[3]

Solution 4:[4]

Solution 5:[5]

Step 1:

Step 2:

Solution 6:[6]

Solution 7:[7]

Solution 8:[8]

Solution 9:[9]

Solution 10:[10]

Solution 11:[11]

Solution 12:[12]

Solution 13:[13]

Solution 14:[14]

Solution 15:[15]

Solution 16:[16]

Solution 17:[17]

Solution 18:[18]

Solution 19:[19]

Solution 20:[20]

Solution 21:[21]

Solution 22:[22]