Lumen bootstrap/app.php provider and middleware registration during upgrade to Laravel

Answer the question first

When moving a Lumen 10.x API to Laravel 10 or 11, the lines you uncomment in bootstrap/app.php are not copied over. Laravel expects middleware in app/Http/Kernel.php and service providers in config/app.php (Laravel 10) or bootstrap/providers.php (Laravel 11).

Confirmed facts

• Lumen registers middleware via $app->middleware([...]) and providers via $app->register(Provider::class). Laravel does not use bootstrap/app.php for these registrations.
• Middleware classes that depend only on Illuminate\Http\Request and return a response work unchanged; only their registration location changes.
• Providers under the namespace Illuminate\Lumen\Providers have no Laravel equivalent and must be replaced by Laravel’s core providers (e.g., AuthServiceProvider, RouteServiceProvider).

Likely explanation

Most third‑party providers enabled in Lumen map one‑to‑one to Laravel and can be re‑registered in the provider config. Providers that rely on Lumen‑specific features (e.g., direct router access) may need boot‑order tweaks or facade aliases because Laravel loads a full request lifecycle with sessions, views, events, and broadcasting enabled by default.

Steps for this case

1. Extract the current Lumen registrations: copy every class listed in $app->middleware and $app->register from bootstrap/app.php into a temporary list.
2. Map middleware to Laravel’s Kernel:
   1. Global middleware → $middleware in app/Http/Kernel.php.
   2. If you want the middleware to run only on API routes, add it to $middlewareGroups['api'].
   3. For named, route‑specific middleware, add an entry to $routeMiddleware (key → class).
3. Map service providers:
   1. Discard any class under Illuminate\Lumen\Providers and replace it with the Laravel counterpart (e.g., Illuminate\Lumen\Providers\AuthServiceProvider → Illuminate\Auth\AuthServiceProvider).
   2. For all other providers, add the class name to the providers array:
      • Laravel 10: config/app.php → 'providers'.
      • Laravel 11: bootstrap/providers.php (return array).
   3. If a provider uses $app->router or other Lumen internals, replace $app with $this (the container) and remove Lumen‑only calls.
4. Verify boot order and facades:
   1. Keep provider dependency order as it was; run php artisan config:cache after changes to catch mis‑ordered dependencies.
   2. Ensure any facade alias a provider expects exists in config/app.php → 'aliases' (Laravel 10) or the appropriate facade service provider (Laravel 11).
5. Test the migration:
   1. Run php artisan route:list to confirm routes.
   2. Hit an endpoint that previously used middleware and check expected behavior (headers, auth, throttling).
   3. Check logs for provider boot errors; adjust any Lumen‑specific code.
6. Clean up Lumen remnants:
   1. Remove or comment out bootstrap/app.php (Laravel ignores it).
   2. Delete Lumen‑only Composer packages that are no longer needed.

Ask for one missing diagnostic detail

To finalize the mapping, could you share the exact list of middleware and provider classes currently enabled in your bootstrap/app.php? This will let us confirm which are Lumen‑only and which can be copied verbatim.