Problems in Laravel Cloud (Nwidart Laravel Modules)

[frosty zodiac]

Hi guys, i'am a new member here and maybe any person can help me with my problems when deploying my project in Laravel Cloud. So, the problems is i try to deploying my Laravel project into Laravel Cloud, and i have an error like in my image, or like this

> @php artisan package:discover --ansi
{"message":"Module [Sales] does not exist!","context":{"exception":{"class":"Nwidart\\Modules\\Exceptions\\ModuleNotFoundException","message":"Module [Sales] does not exist!","code":0,"file":"/var/www/html/vendor/nwidart/laravel-modules/src/FileRepository.php:290"}},"level":400,"level_name":"ERROR","channel":"local","datetime":"2025-03-06T13:52:48.372192+00:00","extra":{}}

In FileRepository.php line 290:
                                  
  Module [Sales] does not exist!  
                                  

Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 1

For modules package, i used nwidart/laravel-modules. Maybe any person can help me with this?

[patent thorn]

That just seems like an error from the package you're using, not caused by Cloud.

[snow marlin]

It feels like a class that has the wrong namespace

[frosty zodiac]

Thank u for reply this post sir. I know about that, but i try to solve that problem with every way, but i have a same results. In local development, there is no problem, this issue only in Laravel Cloud.

[snow marlin]

try to run composer du in your local enviorment

[patent thorn]

Don't think the issue is Cloud. But rather, something like file casing. Your local machine might have a case-insensitive filesystem, while a server usually does have a case-sensitive filesystem.

[snow marlin]

Some file erros do not appear on local development since we do not optimize it by caching

So composer/php do not resolve the error

But when you run commands like composer du that generates the autoload

it show the error warning

i could be wrong, but this is my guess

[frosty zodiac]

So, what should i do to solve this error sir? Maybe a way to show the error in local machine.

[frosty zodiac]

Hmm, i already run this command composer du, but there is not showing errors.

[snow marlin]

Go to your FileRepository

at the imports and see how the Module sales is being called

after that go to the Sales File and check their namespace

[frosty zodiac]

I found a way to solve this problem, but it's only changed the dir name to Modules (default by package). Before it, i used modules name, but i still don't know how to solve this problem when i used this dir name.