Reputation: 2203

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?

Upvotes: 180

Answers (26)

Michael Sarto

Reputation: 21

The issue Undefined index: name in PackageManifest.php occurs due to compatibility problems between Laravel 5.5 and Composer v2. According to this Composer GitHub issue discussion, the solution is to update Laravel to at least version 5.5.49, which includes the necessary adjustments to support Composer v2.

Steps to Resolve:

Update Laravel Framework: Update your composer.json file to specify Laravel 5.5.49 or later in the require section:
```
"require": {
    "laravel/framework": "5.5.49"
}
```
Run Composer Update: After modifying the composer.json, run:
```
composer update
```
Verify Compatibility: Ensure that all other dependencies are compatible with Laravel 5.5.49. If any issues arise, consider updating or replacing those packages.

By upgrading to Laravel 5.5.49, you can continue using Composer v2 without encountering the Undefined index: name error.

Upvotes: 0

Pulkit Modi

Reputation: 2865

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 these lines after the line you just commented:

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

The whole block might look like this (with added comments)

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

        // get all the files from the path
        $installed = json_decode($this->files->get($path), true);

        // if installed contains packages key, use it, otherwise use the whole thing
        $packages = $installed['packages'] ?? $installed;
    }

Upvotes: 260

Jack Damasco

Reputation: 11

I've identified the root cause of this issue. The problem is that you've updated your machine's PHP version to a higher version, while your Laravel version is still below 6.20.

To fix this, please update your Laravel version by following these steps:

Update the 'laravel/framework' package to the latest version in the 6.x series. Run 'composer update' to update your project's dependencies. Finally, run 'composer install' to ensure all dependencies are properly installed.

Upvotes: 0

Prashant Malla

Reputation: 49

I got this issue because of a Laravel and composer version are not compatible.

Following are the steps I follow to solve this issue:

I update Laravel version from 6.1 to 6.20 in composer.json file Eg: "laravel/framework": "6.20.*"
then delete composer.lock file.
And run composer install command

Now Problem is fixed. :)

Upvotes: 1

epheser

Reputation: 565

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.

sudo composer self-update --1

I hope it'll work.

Upvotes: 50

ChimeraTheory

Reputation: 493

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

Upvotes: 2

Sk Shoyeb

Reputation: 167

The easiest way to solve this issue is

delete composer.lock file from your project.

Run composer install

Upvotes: 11

Webkix

Reputation: 281

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

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

Upvotes: 1

Bedram Tamang

Reputation: 4365

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

Upvotes: 47

Burhan Ibrahimi

Reputation: 377

If you want to fix without making updates and composer updates

just go to vendor/composer and remove installed.json

Upvotes: 3

Chinthaka Dilan F

Reputation: 615

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;

Upvotes: 3

Martin Muñoz

Reputation: 516

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.

Upvotes: 3

KeitelDOG

Reputation: 5180

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.

Upvotes: 1

Ashiq KS

Reputation: 145

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

Upvotes: 6

Jos Koomen

Reputation: 372

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

Upvotes: 8

Prograymer

Reputation: 11

To downgrade composer to an old version:

composer self-update <version>

Example:

composer self-update 1.10.1

Upvotes: 1

Gandhist

Reputation: 89

Running composer update worked for my project with Laravel 5.7

Upvotes: 5

Lan Danel

Reputation: 53

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.

Upvotes: 0

DavidHyogo

Reputation: 2898

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

Upvotes: 67

truongnm

Reputation: 2474

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

Upvotes: 21

Nabil

Reputation: 33

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

Upvotes: 3

Abrar Ahmad

Reputation: 430

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"

Upvotes: 13

Will Bin Lopes Cordeiro

Reputation: 2217

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.

Upvotes: 220

Gerardo Argueta

Reputation: 301

In my case downgrading the composer version fixed the problem.

sudo composer self-update --1

Upvotes: 20

Маргарита Козачек

Reputation: 311

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

Upvotes: 31

Nick Zinger

Reputation: 1174

Running the following command fixed it for us

composer self-update --stable

Upvotes: 2

Laravel PackageManifest.php: Undefined index: name

Answers (26)

Steps to Resolve:

Step 1

Step 2

Step 3

Step 1:

Step 2:

Related Questions