Reputation: 760
Loading composer repositories with package information Updating dependencies (including require-dev) Package operations: 0 installs, 0 updates, 1 removal - Removing genealabs/laravel-caffeine (0.3.12) Writing lock file Generating optimized autoload files
Illuminate\Foundation\ComposerScripts::postAutoloadDump @php artisan package:discover
[Symfony\Component\Debug\Exception\FatalThrowableError]
Class 'GeneaLabs\LaravelCaffeine\LaravelCaffeineServiceProvider' not found
Script @php artisan package:discover handling the post-autoload-dump event returned with error code 1
Upvotes: 72
Views: 364071
Reputation: 521
In case you're coming from a google search, make sure that you have a .env file in which APP_ENV is set to local. (if you cloned a project from github, the first thing is to run cp .env.example .env
. or in windows copy .env.example .env
That was actually the problem in my case)
Then run composer install
again.
Upvotes: 28
Reputation: 1
if you cloned a project from github, the first thing is to run cp .env.example .env.
Then run composer install again.
That was actually the problem in my case
this is idea from @Itope84
Upvotes: 0
Reputation: 1
Please check first artisan file present in root folder and this error is occurred because some file is missing from your project, download new laravel project and check all files with your existing project
Upvotes: 0
Reputation: 21
If composer update
and composer install
not work then you can try this composer require laravel/sanctum
Upvotes: 0
Reputation: 51
You could try
composer update
That worked for me when I had this same issue. In my case what made me discover this issue was when i tried to run the artisan command and it didn't return anything
So I tried composer dumpautoload which threw me this same error mentioned
composer update did the trick
Upvotes: 4
Reputation: 2023
step 1: create .env file
step 2: create storage folders and sub folder
step3: run command composer install
again
Upvotes: 0
Reputation: 1153
In my case this error happened to me when i removed a package with composer remove
, then i realized somehow, something affected my config files in config
directory, and they all become empty.
Solution for me was simply getting those files from Laravel
repository and copy them into config
directory. (and of course in case you need to do vendor publish for specific libraries, you should do it again.)
Upvotes: 1
Reputation: 594
My solution was creating the storage/framework/cache/data/cache folder and gave it permissions
Upvotes: 2
Reputation: 1
in my case this was the error
> @php artisan package:discover --ansi
In AuthServiceProvider.php line 29:
syntax error, unexpected '=>' (T_DOUBLE_ARROW), expecting ')'
Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 1
I solved it by upgrading PHP version to 7.4
because i was using Arrow functions in the AuthServiceProvider that came up in 7.4
Upvotes: 0
Reputation: 186
Running the command php artisan package:discover --ansi
by itself might tell you more about the issue.
In my case correcting a character out of place in the .env
solved it.
Upvotes: 4
Reputation: 410
I have same issue
above this error
Script @php artisan package:discover handling the post-autoload-dump event returned with error code 1
I found one more message in my terminal like: "
"Cartalyst\Stripe\Laravel\StripeServiceProvider::class, not found in your ProviderRepository.php"
then i go config/app.php and find
Cartalyst\Stripe\Laravel\StripeServiceProvider::class
comment it out then run
composer update
it will work fine **In your case maybe package name is different please check your terminal **
Upvotes: 0
Reputation: 469
in my case the problem was into outdated "../bootstrap/cache/packages.php and services.php"
I have had to. drop those files and rerun composer install...
Erroneous data format for unserializing 'Symfony\Component\Routing\CompiledRoute'
Script @php artisan package:discover handling the post-autoload-dump event returned with error code 1
Upvotes: 0
Reputation: 4823
If none of the solutions work for you, the handling the post-autoload-dump event returned with error code 1 error can also be caused by using Composer 2
instead of Composer 1
. That can happen when you run the install command manually in something like a Dockerfile, and it installs newest. Just modify your command to install the last 1.x.x stable version with the --1
option:
curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin --filename=composer --1
Or, specify a certain version with --version=x.x.x
:
curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin --filename=composer --version=1.10.17
It might be good to also delete your vendor
directory and composer.lock
file so that nothing stale interferes with the version downgrade, before calling composer install
as usual.
Upvotes: 0
Reputation: 339
remove the config.php file located in bootstrap/cache/ enter link description here
that's works with me
Upvotes: -2
Reputation: 431
I needed rollback for the 1.9.x version, in 2.x.x not work
composer self-update --rollback
Upvotes: 3
Reputation: 69
In my case, I had left over references to classes in a recently removed composer package. In your laravel app, check config/app.php
, particularly the providers
and aliases
properties, for references to the class specified in the error.
Upvotes: 3
Reputation: 1766
in this case, I use space
for APP_NAME
key in .env
file.
and have below error :
The environment file is invalid!
Failed to parse dotenv file due to unexpected whitespace. Failed at [my name].
Script @php artisan package:discover handling the post-autoload-dump event returned with error code 1
Don't use space
in APP_NAME
key !!
Upvotes: 2
Reputation: 449
This happened to me because I had a ddd()
or dd()
;die; in my routes/web.php file I forgot about.
Upvotes: 3
Reputation: 213
In case the error appears when upgrading from Laravel 6 to Laravel 7, the command composer require laravel/ui "^2.0"
solves the problem (see https://laravel.com/docs/7.x/upgrade#authentication -scaffolding)
Upvotes: 4
Reputation: 272
I came across this when upgrading from 5.8 to 6.x.
I had str_slug()
in config/cache.php
and config/session.php
.
I have changed it to Str::slug()
and the error has disappeared.
See https://laravel.com/docs/6.x/upgrade#helpers.
Upvotes: 2
Reputation: 792
I simply ran composer update
and it resolved my issue -
Laravel 6.*
Upvotes: 66
Reputation: 2835
My problem was fideloper proxy
version.
when i upgraded laravel 5.5 to 5.8 this happened
just sharing if anybody get help
change you composer json fideloper version:
"fideloper/proxy": "^4.0",
After that you need to run update composer that's it.
composer update
Upvotes: 4
Reputation: 57
Check your code for errors in my case i had an error in Kernel.php. First solve errors if any Than run composer require ....(package you wish)
Upvotes: -1
Reputation: 559
You have added the service provider in config/app.php for the package that is not installed in the system.
You must have this line in your config/app.php. You can either remove it or install the package GeneaLabs\LaravelCaffeine\LaravelCaffeineServiceProvider
See https://github.com/GeneaLabs/laravel-caffeine.
Run the line below via CLI to install the package.
composer require genealabs/laravel-caffeine
Upvotes: 6
Reputation: 634
Add this in composer.json
. Then dusk has to be installed explicitly in your project:
"extra": {
"laravel": {
"dont-discover": [
"laravel/dusk"
]
}
},
Upvotes: 35