View

Introduction#

The view component allows you to render templates using the Blade templating engine. This is useful whenever your console application needs to produce something more structured than terminal output — an HTML report, a generated configuration file, or the body of an email.

Note: If all you want is beautifully styled terminal output, you don't need this component. Every Laravel Zero application already includes Termwind.

Installation#

You may install the view component using the app:install Artisan command:

php application app:install view

The installer will require illuminate/view, create the resources/views directory where your templates live, create a config/view.php configuration file, and prepare storage/framework/views for compiled templates.

Rendering Views#

Views may be rendered using the View facade or the global view helper. Both accept the name of the view and an array of data that should be made available to it:

use Illuminate\Support\Facades\View;

$html = View::make('report', ['movies' => $movies])->render();

$html = view('report', ['movies' => $movies])->render();

Assuming the view above lives at resources/views/report.blade.php:

<ul>
    @foreach ($movies as $movie)
        <li>{{ $movie->title }}</li>
    @endforeach
</ul>

Consult the Blade documentation on the Laravel website for the full templating syntax.

Using Views in a Build#

Blade compiles your templates to plain PHP files and writes them to the path defined by the compiled option of your config/view.php configuration file. By default, that path is storage/framework/views, which lives inside your PHAR archive and is therefore read-only.

To handle this, point the compiled option at a writable location whenever the application is running from within an archive:

<?php

return [
    'paths' => [
        resource_path('views'),
    ],

    'compiled' => \Phar::running()
        ? sys_get_temp_dir()
        : env('VIEW_COMPILED_PATH', realpath(storage_path('framework/views'))),
];

Your templates also need to be part of the build itself. Add the resources directory to the directories section of your box.json file:

"directories": [
    "app",
    "bootstrap",
    "config",
    "resources",
    "vendor"
],