183

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?

Improve this question
3
  • 3
    I had a same issue, but on my local env (docker). I fixed it by using composer update outside docker container, so basically using php and composer installed on my Mac. If you use docker you can try to do the same thing, maybe not the best way how to fix it but it works. :) Commented Apr 13, 2020 at 12:40
  • here's a solution that worked for me. github.com/composer/composer/issues/9340#issuecomment-716210369 change your laravel framework to 6.18.7 so that its compatible with composer 2 Commented Apr 8, 2021 at 19:05
  • I tried so many answers below but only stackoverflow.com/questions/61177995/… worked for me. Commented Apr 21, 2021 at 15:02

26 Answers 26

Reset to default
259

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;
    }
Improve this answer
Sign up to request clarification or add additional context in comments.

11 Comments

The problem here is I just don't want to change the core files.
This is not a great solution. You should not edit vendor files like that. What if somebody else install your dependencies from your composer.lock.json?
For a temporary fix it works like a charm.
Running composer update now makes that change to PackageManifest.php without any need for manual editing.
Never make a change in core files in vendor directory
|
222

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.

Improve this answer

6 Comments

I don't know why people accept downgrading composer or changing the source files of Laravel as a solution, while this is the right way to fix it.
@shamaseen because you don't want to run "composer update" on a production environment.
This will update all your library files to their latest version constrained by composer.json. You may or may not want to do this. getcomposer.org/doc/03-cli.md#update-u
This works, the situation is that all dependencies will be updated to the latest version and probably some scripts will break, so take that on consideration.
This did not work for me
|
68

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
Improve this answer

4 Comments

This reply works for me when upgrading Laravel 5.5 to 6.x
Use composer self-update --rollback to return to version 2.0.13
works for me too
Thank you, your answer fixed the problem but didn't clearly explain why. The actual problem is that the laravel version we're running is not compatible with composer 2.x. Both downgrading composer to 1.x or upgrading to a compatible laravel fix the problem. github.com/composer/composer/issues/9340#issuecomment-716210369
52

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.

Improve this answer

8 Comments

how you downgrade it?
This is only a correct temporary workaround if composer update doesn't fix it. Downgrading Composer is not a solution.
I downgraded from 2.0.11 to 1.10.20 using composer self-update 1.10.20 and the error disappeared. But I cannot update to composer 2.x....
Instead of composer install, you can use composer update. It works for me
composer self-update --1 ... this command helped me
|
47

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
Improve this answer

7 Comments

This solved it for me too without need to downgrade composer. I think this should be the approved answer. Perhaps downgrading composer also solves it, but in my case and in my opinion it's less ideal to downgrade.
i think this is the same of not deleting the composer.lock file and just run composer update.
@kapitan It is not. composer update looks into composer.lock file and updates each dependencies to newer version, if newer version is available. But composer install with deleting composer.lock file doesn't care what has been previously installed, it installs everything as fresh of composer.json file
@BedramTamang -I actually knew what's happening on both cases. I am actually talking about the version of the packages that will be installed at the end because both will install the newest package.
this one should be marked as correct answer.
|
31

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

Improve this answer

2 Comments

I'm afraid this didn't work for me. I still got the same error: In PackageManifest.php line 122: Undefined index: name
This worked for me and I prefer it over updating all the packages
21

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

Improve this answer

1 Comment

Thank you!!! I must have updated to Composer 2 at some point but was still running Laravel 6.0 in this repo. I needed to do a LOT of manual upgrades to get this working. But what you pointed to was definitely my problem. Thanks.
20

In my case downgrading the composer version fixed the problem.

sudo composer self-update --1
Improve this answer

Comments

14

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"

Improve this answer

4 Comments

Looks like there may be a few different causes of this issue, each with different solutions, but this was what worked for me. In context, upgrading from 5.8 where every .1 is a major version change, but on 6+ every .1 is a minor version. So locking to "6.0" or "6.0.*" kept it on "6.0.4" and avoided the rest of the version updates (currently "6.20.16") This bug existed on "6.0.4" but was fixed after.
I also faced the same issue but couldn't fix it by applying almost all solutions listed here. However, this solution triggered something in me and I checked my framework version once again and found that it was entered wrongly(I was testing something on the previous day). I put the right framework number and the issues got disappeared instantly. Thank You!
This was the solution to migrating from Laravel 5.8 to 6.0. Thanks, you saved me some time.
thank you so much ... same issue i mistakenly add laravel/framework": "6.0"..."laravel/framework": "^6.0" this fixed my issue
12

The easiest way to solve this issue is

delete composer.lock file from your project.

Run composer install

Improve this answer

1 Comment

Warning: this will update all packages. If you want to avoid updating packages, go to vendor/composer and remove installed.json
8

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

Improve this answer

Comments

6

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
Improve this answer

1 Comment

Please add some explanation to your answer such that others can learn from it
5

Running composer update worked for my project with Laravel 5.7

Improve this answer

1 Comment

This may be the correct answer but another user has already posted something similar. When writing a new answer please try to include additional information or examples that the other answers don't have.
4

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;
Improve this answer

4 Comments

never change the vendor source files. This changes will be overwritten on new update
still no side effect for me. @natghi
@AnujShrestha you are correct. still, I have not met that issue again when I updated
it is because the package manager has not updated that specific file, but if they change the file, then all the update you did in the vendor folder will be gone on the next composer update. And there are many proper answers for this issue already. Yours is just bad practice.
3

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

Improve this answer

Comments

3

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.

Improve this answer

Comments

3

If you want to fix without making updates and composer updates

just go to vendor/composer and remove installed.json

Improve this answer

1 Comment

Sadly, this doesn't seem to fix the undefined index: name issue
2

Running the following command fixed it for us

composer self-update --stable
Improve this answer

1 Comment

This didn't work for me. I got the message You are already using composer version 2.0.4 (stable channel).
2

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
Improve this answer

Comments

1

To downgrade composer to an old version:

composer self-update <version>

Example:

composer self-update 1.10.1
Improve this answer

Comments

1

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.

Improve this answer

Comments

1

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

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

Improve this answer

Comments

1

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

Following are the steps I follow to solve this issue:

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

Now Problem is fixed. :)

Improve this answer

Comments

0

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

the solution is :

  1. Delete Vendor folder inside your project if exist.
  2. 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
  3. then composer update

finally, it works perfectly.

Improve this answer

1 Comment

Please don't forget to visit the Laravel docs upgrade guide, if you are increasing the framework version. laravel.com/docs/6.x/upgrade
0

enter image description here

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.

Improve this answer

1 Comment

Please read Why should I not upload images of code/data/errors? to see how you can improve your answer.
0

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:

  1. 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"
}

  2. Run Composer Update: After modifying the composer.json, run:

    composer update

  3. 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.

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.