Laravel PackageManifest.php line 131: Undefined index: name

Question

I updated the composer with this command:

composer self-update

It was updated to version 2.0.4. Then when I tried to launch my Laravel project using:

php artisan serve

I got this error:

In PackageManifest.php line 131:

 Undefined index: name

I tried getting back to the old version of the composer with this:

composer self-update --rollback

The composer was downgraded to version 1.9.3, but it didn't help with the error. Then I used this command to update the composer again:

composer self-update --stable

And still got the same error.

This is the line 131 of the PackageManifest.php file:

return [$this->format($package['name']) => $package['extra']['laravel'] ?? []];

After using composer self-update to update version of composer, did you tried to run againcomposer update before running php artisan serve? — Thân LƯƠNG Đình
– Thân LƯƠNG Đình, Commented Oct 31, 2020 at 11:00
First, you should check again version after using composer self-update. Then, you try composer update. Finally, you run php artisan serve — Thân LƯƠNG Đình
– Thân LƯƠNG Đình, Commented Oct 31, 2020 at 11:05

Thân LƯƠNG Đình · Accepted Answer · 2020-10-31 11:09:33Z

70

First, you should check again version after using composer self-update. Then, you try composer update. Finally, you run php artisan serve.

answered Oct 31, 2020 at 11:09

Thân LƯƠNG Đình

3,2402 gold badges15 silver badges22 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

video-reviews.net · Accepted Answer · 2021-07-23 11:15:34Z

25

The issue is one of the Laravel default vendor packages has a small bug.

The solution to fix this is the following:

rm -rf composer.lock
rm -rf vendor
composer install

This will update the composer packages to the latest versions for your current version of laravel and this should resolve the issue.

edited Jul 23, 2021 at 11:15

answered Jan 19, 2021 at 7:48

video-reviews.net

2,94624 silver badges17 bronze badges

Comments

Sethu · Accepted Answer · 2021-02-08 08:43:29Z

14

This was actually fixed in Laravel already, so please make sure you update Laravel to at least 6.18.7+ or 7.6.0+ or 8.0+

FYI, if you remove composer local file, it will update all your dependencies, so it's not a good idea.

By running the command composer update laravel/framework should hopefully fix the issue and not cause any other problems. If you can not update Laravel then you better off downgrade to Composer 1 using composer self-update --1.

If you are using illuminate/foundation instead of laravel/framework, then make sure you composer update illuminate/foundation instead.

answered Feb 8, 2021 at 8:43

Sethu

1,37912 silver badges14 bronze badges

2 Comments

saber tabatabaee yazdi Over a year ago

this helped me : downgrade to Composer 1 using composer self-update --1

icosmin Over a year ago

Downgrading composer to version 1 (which same version on production server) was the best solution. The whole purpose of having of local environment is to be as similar to production as possible. Thanks!

Solo.dmitry · Accepted Answer · 2021-02-01 14:11:51Z

8

add code in Illuminate\Foundation\PackageManifest.php about to line 129:

    ...
    $ignoreAll = in_array('*', $ignore = $this->packagesToIgnore());
    // ------------------:::::::::FIX::::::::::------------
    if (isset($packages['packages'])){
        $packages = $packages['packages'];
    }
    // ---------------------------ENDFIX-------------------
    $this->write(collect($packages)->mapWithKeys(function ($package) {
    ...

answered Feb 1, 2021 at 14:11

Solo.dmitry

79012 silver badges16 bronze badges

5 Comments

Solo.dmitry Over a year ago

Of course. But sometimes we need to ignore rules, becouse the life is more complicated then rules. This is one of these cases. this fix make composer workable to update the saint vendor folder too. You can publish your decision better than this.

Snapey Over a year ago

then one day you are left scratching your head because you did something stupid and ignored the rules. The solution is already posted here from @advertmanagerpro.com

Solo.dmitry Over a year ago

He offers an ax, and I offer a scalpel, both tools solve the problem, the choice is up to the user

Ngugi Kiarie Over a year ago

This worked for me, although my edit was done on line 121, not 129

video-reviews.net Over a year ago

I agree with @Snapey, you should never change code directly inside the vendor folder. As you will very likely loose it as soon as you do a composer update or try to install a new composer package. Plus most people have the vendor folder in the .gitignore file so the vendor folder will never get saved to backup repositories like github or similar. It is bad practice to make changes inside the vendor folder.

Son Andreas · Accepted Answer · 2021-02-26 04:21:26Z

5

Option 1:

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

then search code :

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

insert

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

Option 2 :

run command

composer update

answered Feb 26, 2021 at 4:21

Son Andreas

661 silver badge3 bronze badges

Comments

saber tabatabaee yazdi · Accepted Answer · 2021-05-05 16:04:50Z

2

this helped me :

downgrade to Composer 1 using

composer self-update --1

answered May 5, 2021 at 16:04

saber tabatabaee yazdi

4,9953 gold badges53 silver badges63 bronze badges

Collectives™ on Stack Overflow

Laravel PackageManifest.php line 131: Undefined index: name

6 Answers 6

Comments

Comments

2 Comments

5 Comments

Comments

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

6 Answers 6

Comments

Comments

2 Comments

5 Comments

Comments

Comments

Linked

Related