ViewServiceProvider dependency in Validation Errors and Health Endpoint

[priyashpatil]

Laravel Version

11

PHP Version

8.2

Database Driver & Version

MySQL 8 - Docker

Description

Since Lumen is no longer maintained, there must be some way to have API only configuration. I'm trying to build a micro service using Laravel 11. A simple service which would just take data -> process it and then -> store into database.

Now here I don't want to use any other service providers that are not needed for example I have disabled: Sessions, Authentication, Mail, removed default models, migrations and more.

But It looks like the framework requires ViewServiceProvider for validation errors thrown via validate methods and also for health endpoint. Currently getting:

    "message": "Target class [view] does not exist.",
    "exception": "Illuminate\\Contracts\\Container\\BindingResolutionException",

Steps To Reproduce

bootstrap/app.php

<?php

use Illuminate\Foundation\Application;
use Illuminate\Foundation\Configuration\Exceptions;
use Illuminate\Foundation\Configuration\Middleware;
use Illuminate\Http\Request;

return Application::configure(basePath: dirname(__DIR__))
    ->withRouting(
        api: __DIR__ . '/../routes/api.php',
        apiPrefix: '/',
        health: '/health',
    )
    ->withMiddleware(function (Middleware $middleware) {
        //
    })
    ->withExceptions(function (Exceptions $exceptions) {
        $exceptions->shouldRenderJsonWhen(function (Request $request, Throwable $e) {
            return true; // forces JSON response
        });
    })->create();

config/app.php

    /**
     * By default providers are loaded from \Illuminate\Support\DefaultProviders::class
     * Laravel 11 first looks for this config in config/app.php to allow
     * overriding the default providers.
     *
     * @var array
     */
    'providers' => [
        // \Illuminate\Auth\AuthServiceProvider::class,
        // \Illuminate\Broadcasting\BroadcastServiceProvider::class,
        // \Illuminate\Bus\BusServiceProvider::class,
        \Illuminate\Cache\CacheServiceProvider::class,
        \Illuminate\Foundation\Providers\ConsoleSupportServiceProvider::class,
        // \Illuminate\Concurrency\ConcurrencyServiceProvider::class,
        // \Illuminate\Cookie\CookieServiceProvider::class,
        \Illuminate\Database\DatabaseServiceProvider::class,
        \Illuminate\Encryption\EncryptionServiceProvider::class,
        \Illuminate\Filesystem\FilesystemServiceProvider::class,
        \Illuminate\Foundation\Providers\FoundationServiceProvider::class,
        // \Illuminate\Hashing\HashServiceProvider::class,
        // \Illuminate\Mail\MailServiceProvider::class,
        // \Illuminate\Notifications\NotificationServiceProvider::class,
        // \Illuminate\Pagination\PaginationServiceProvider::class,
        // \Illuminate\Auth\Passwords\PasswordResetServiceProvider::class,
        // \Illuminate\Pipeline\PipelineServiceProvider::class,
        \Illuminate\Queue\QueueServiceProvider::class,
        // \Illuminate\Redis\RedisServiceProvider::class,
        // \Illuminate\Session\SessionServiceProvider::class,
        \Illuminate\Translation\TranslationServiceProvider::class,
        \Illuminate\Validation\ValidationServiceProvider::class,
        // \Illuminate\View\ViewServiceProvider::class,
    ],

routes/api.php

use Illuminate\Http\Request;
use Illuminate\Support\Facades\Route;

Route::post('/push', function (Request $request) {
    $validated = $request->validate([
        'name' => 'required'
    ]);

    // process data

    return ['status' => 'ok'];
});

Now sending data to /push endpoint or visiting /health will throw 500 error.

    "message": "Target class [view] does not exist.",
    "exception": "Illuminate\\Contracts\\Container\\BindingResolutionException",

[priyashpatil]

Attaching composer.json for reference. The case is also same with Laravel 12:

{
    "$schema": "https://getcomposer.org/schema.json",
    "name": "laravel/laravel",
    "type": "project",
    "description": "The skeleton application for the Laravel framework.",
    "keywords": [
        "laravel",
        "framework"
    ],
    "license": "MIT",
    "require": {
        "php": "^8.2",
        "laravel/framework": "^12.0",
        "laravel/octane": "^2.8",
        "laravel/tinker": "^2.10.1"
    },
    "require-dev": {
        "fakerphp/faker": "^1.23",
        "laravel/pint": "^1.13",
        "mockery/mockery": "^1.6",
        "nunomaduro/collision": "^8.6",
        "phpunit/phpunit": "^11.5.3"
    },
    "autoload": {
        "psr-4": {
            "App\\": "app/",
            "Database\\Factories\\": "database/factories/",
            "Database\\Seeders\\": "database/seeders/"
        }
    },
    "autoload-dev": {
        "psr-4": {
            "Tests\\": "tests/"
        }
    },
    "scripts": {
        "post-autoload-dump": [
            "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",
            "@php artisan package:discover --ansi"
        ],
        "post-update-cmd": [
            "@php artisan vendor:publish --tag=laravel-assets --ansi --force"
        ],
        "post-root-package-install": [
            "@php -r \"file_exists('.env') || copy('.env.example', '.env');\""
        ],
        "post-create-project-cmd": [
            "@php artisan key:generate --ansi",
            "@php -r \"file_exists('database/database.sqlite') || touch('database/database.sqlite');\"",
            "@php artisan migrate --graceful --ansi"
        ]
    },
    "extra": {
        "laravel": {
            "dont-discover": []
        }
    },
    "config": {
        "optimize-autoloader": true,
        "preferred-install": "dist",
        "sort-packages": true,
        "allow-plugins": {
            "pestphp/pest-plugin": true,
            "php-http/discovery": true
        }
    },
    "minimum-stability": "stable",
    "prefer-stable": true
}

[mbabker]

For the health endpoint, you'll need to make your own route as Taylor has repeatedly rejected PRs to make the one built into the framework do anything but serve an HTML document.

For validation errors, as long as the exception handler is handling a Illuminate\Validation\ValidationException then it should be building a JSON response with the code you've set up unless something is setting the exception's $response property before it gets to the exception handler. But a full stack trace and knowing what kind of exception is being handled would be a bit more helpful than the container's exception resolving the view service.

[priyashpatil]

It looks like there's a lot of overriding needs to be done. Recently sentry caught some errors requiring AuthServiceProvider for Gate usage somewhere. I guess Symfony is way to here.