PHPackages                             miko/laravel-latte - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Templating & Views](/categories/templating)
4. /
5. miko/laravel-latte

ActiveLibrary[Templating & Views](/categories/templating)

miko/laravel-latte
==================

Latte template engine for Laravel

3.1.1(2mo ago)43.6k2[2 issues](https://github.com/miloslavkostir/laravel-latte/issues)1MITPHPPHP >=8.2

Since Feb 28Pushed 2mo ago1 watchersCompare

[ Source](https://github.com/miloslavkostir/laravel-latte)[ Packagist](https://packagist.org/packages/miko/laravel-latte)[ RSS](/packages/miko-laravel-latte/feed)WikiDiscussions master Synced 2d ago

READMEChangelog (10)Dependencies (24)Versions (20)Used By (1)

Laravel Latte
=============

[](#laravel-latte)

Extends the Laravel framework with the templating engine [Latte](https://latte.nette.org)

Installation
------------

[](#installation)

```
$ composer require miko/laravel-latte

```

Then the templating engine is used according to the file extension:

- `*.blade.php` - [Blade (Laravel default)](https://laravel.com/docs/blade)
- `*.latte` - [Latte](https://latte.nette.org)

⚠️ **Latte 3.1 compatibility notice**Be aware that Latte 3.1 introduces breaking changes in [HTML attribute rendering](https://latte.nette.org/en/html-attributes) — most notably, `null` values now cause attributes to be omitted entirely, and boolean attributes behave differently compared to 3.0. If your templates rely on the previous behavior, a `composer update` may produce unexpected output. To stay on the safe 3.0 branch, pin the dependency in your project's `composer.json`:

```
"require": {
    "miko/laravel-latte": "^3.0",
    "latte/latte": "3.0.*"
}
```

See the recommended [migration guide](#migration-to-3-1).

Configuration
-------------

[](#configuration)

Publish config file into `config/latte.php`:

```
$ php artisan vendor:publish --provider="Miko\LaravelLatte\ServiceProvider"
```

Follow the instructions in the config file.

And that's it! If you want more control, [override the service provider](#custom-extension).

Extension
---------

[](#extension)

The following features are not available in native Latte or behave differently (e.g., tags `{link}`, `{asset}` or translations). These features extend Latte with useful helpers and implement Laravel features into the Latte engine. On the other hand, features that work in Latte only with the Nette framework or Nette components are not available here (e.g. form tags).

### Filter `nl2br` (*bool* $xhtml = `null`)

[](#filter-nl2br-bool-xhtml--null)

```
{$text|nl2br}
{$text|nl2br: true}
```

> Default rendering as xhtml or html can be configured in the config file.

### Tags `{link}` and `n:href`

[](#tags-link-and-nhref)

Similar to [tags in Nette](https://doc.nette.org/en/application/creating-links#toc-in-the-presenter-template)except that the separator between controller and method is not `:` but `@` and the default method is not `default` but `index` according to the Laravel conventions. Basically this is a simplified call to Laravel's [action()](https://laravel.com/docs/urls#urls-for-controller-actions) helper when there is no need to write the entire FQCN and the word `Controller`. In addition, it is possible to use the keyword `this` for the current action - then there is no need to write unchanged parameters.

```
{link User@detail}             {* shortcut for action([App\Http\Controllers\UserController::class, 'detail']) *}
{link User@}                   {* shortcut for action([App\Http\Controllers\UserController::class, 'index']) *}
{link detail}                  {* shortcut for action([$current_controller, 'detail']) *}
{link User@detail 123, 456}    {* shortcut for action([App\Http\Controllers\UserController::class, 'detail'], [123, 456]) *}
{link User@detail foo => bar}  {* shortcut for action([App\Http\Controllers\UserController::class, 'detail'], ['foo' => 'bar']) *}
{link "Admin\Article@detail"}  {* shortcut for action([App\Http\Controllers\Admin\ArticleController::class, 'detail']) *}
{link this}                    {* generates a link for the current action and current arguments (current URL) *}

{* n tag *}

{* Named arguments can be used... *}
product detail
{link Product@show $product->id, lang: cs}

{* ...and (expand) as well because of Latte v2 BC *}
{var $args = [$product->id, lang => cs]}
product detail
{link Product@show (expand) $args}
```

> `(expand)` - the equivalent of `...$arr` operator

#### Usage of `this`

[](#usage-of-this)

route:

```
Route::get('/users/permissions/{user}/{permission}', [\App\Http\Controllers\UserController::class, 'permissions']);
```

template:

```
Sort by date
```

At address `mysite.com/users/permissions/1/2` generates link `mysite.com/users/permissions/1/2?sort=date`

### Tags `{asset}` and `n:src`

[](#tags-asset-and-nsrc)

Adds the `m` parameter to the URL with the timestamp of the last file change. Every time the file is changed, it will be reloaded and there is no need to clear the browser cache:

```

```

### Tags `{csrf}` and `{method}`

[](#tags-csrf-and-method)

Generate hidden inputs `_token` and `_method` in form. See [Preventing CSRF Requests](https://laravel.com/docs/csrf#preventing-csrf-requests)and [Form Method Spoofing](https://laravel.com/docs/routing#form-method-spoofing). Rendering as xhtml or html can be configured in the config file.

```

    {csrf}
    {method PUT}

```

### Tags `{livewire}`, `{livewireStyles}`, `{livewireScripts}` a `{livewireScriptConfig}`

[](#tags-livewire-livewirestyles-livewirescripts-a-livewirescriptconfig)

**🧪 Experimental**
Tags for [Livewire](https://livewire.laravel.com/). They are only available if livewire is implemented.

```

        {livewireStyles}

    {livewire component-name foo => bar}
    {livewireScripts}
    {livewireScriptConfig}

```

Since Livewire renders its templates itself, the template can be a latte or a blade file.

⚠️ **WARNING:** if the component view is a latte file and the default layout is set in config (`latte.layout`), the component view **must have** `{layout none}` at the beginning. Otherwise, Latte engine will try to render the layout again for this component.

`resources/views/livewire/component-name.latte`:

```
{layout none}

    ...

```

### Translation `{_}`

[](#translation-_)

Laravel provides functions `__()` and `trans()` respectively, see [retrieving translation strings](https://laravel.com/docs/localization#retrieving-translation-strings), and `trans_choice()`, see [Pluralization](https://laravel.com/docs/localization#pluralization). The tag `{_}` can handle both, it depends on the second parameter, whether it is an integer or an array.

```
{_'messages.welcome'}
{_'messages.welcome', [name: dayle]}
{_'messages.apples', 10}
{_'time.minutes_ago', 5, [value: 5]}
{_'time.minutes_ago', 5, [value: 5], de}
{_'messages.welcome', locale: de}
```

Above is equivalent to Laravel functions:

```
echo __('messages.welcome');
echo __('messages.welcome', ['name' => 'dayle']);
echo trans_choice('messages.apples', 10);
echo trans_choice('time.minutes_ago', 5, ['value' => 5]);
echo trans_choice('time.minutes_ago', 5, ['value' => 5], 'de');
echo __('messages.welcome', locale: 'de');
```

If you want to implement `Latte\Essential\TranslatorExtension` as described in [Latte doc](https://latte.nette.org/en/develop#toc-translatorextension), you can do so in `ServiceProvider` e.g. like this:

```
use Latte\Essential\TranslatorExtension;
use Miko\LaravelLatte\Runtime\Translator;

public function boot(): void
{
    $latte = $this->app->get(\Latte\Engine::class);
    $latte->addExtension(new TranslatorExtension([Translator::class, 'translate']));
}
```

Why is it not implemented by default?

- `{translate}{/translate}` and `n:translate` tag are tempting to use [translation strings as keys](https://laravel.com/docs/localization#using-translation-strings-as-keys)for an entire paragraph, which seems like hell and leads to error rates.
- `n:translate` doesn't work (v3.0.13)
- setting the `lang` parameter as a cache key for precompiling static texts does not work if the language is set at runtime with `App::setLocale()`

### Components `{x}`

[](#components-x)

An object implementing `Miko\LaravelLatte\IComponent` can be rendered in template:

```
namespace App\View\Components;

use Illuminate\View\View;
use Miko\LaravelLatte\IComponent;

class Alert implements IComponent
{
    private array $params = [];

    /**
     * Get some services from service container
     */
    public function __construct(private SomeService $someService)
    {
    }

    /**
     * Get variables from template
     */
    public function init(...$params): void
    {
        $this->params = $params;
    }

    /**
     * Get the view / contents that represent the component.
     */
    public function render(): View|string
    {
        return view('components.alert', $this->params);
    }
}
```

View:

```
{x alert type => error, message => $message}
```

Root namespace of components is set in config (`latte.components_namespace`) and is `App\View\Components` by default.

⚠️ **WARNING:** if the default layout is set in config (`latte.layout`), the component view **must have** `{layout none}` at the beginning. Otherwise, Latte engine will try to render the layout again for this component.

Custom extension
----------------

[](#custom-extension)

It's possible to overide `Miko\LaravelLatte\ServiceProvider`:

```
// app\Providers\LatteServiceProvider

namespace App\Providers;

use Latte\Engine as Latte;

class LatteServiceProvider extends \Miko\LaravelLatte\ServiceProvider
{
    /**
     * Override this method for custom setup
     * @param \Latte\Engine $latte
     * @return void
     */
    protected function configure(Latte $latte): void
    {
        parent::configure($latte);

        $latte->setSomething($this->config->get('latte.something'));
    }

    /**
     * Override this method for a custom extension
     * https://latte.nette.org/extending-latte
     * @param \Latte\Engine $latte
     * @return void
     */
    protected function extensions(Latte $latte): void
    {
        parent::extensions($latte);

        $latte->addFunction(...);
        $latte->addFilter(...);
        $latte->addExtension(...);
    }
}
```

```
// bootstrap/providers.php

return [
    // ...
    App\Providers\LatteServiceProvider::class,
];
```

Migration from Latte 3.0 to Latte 3.1
-------------------------------------

[](#migration-from-latte-30-to-latte-31)

1\. Install latest `latte/latte` `v3.0`:

```
"require": {
    "miko/laravel-latte": "^3.0",
    "latte/latte": "3.0.*"
}
```

```
composer update -W miko/laravel-latte
```

2\. Set `'strict_types' => true` in `config/latte.php`.
Latte 3.1 has strict types by default. Set it accordingly, check your views and fix the errors.

3\. Install latest `latte/latte` `v3.1`: Lock Latte to `"latte/latte": "3.1.*"` or remove it:

```
"require": {
    "miko/laravel-latte": "^3.0",
}
```

```
composer update -W miko/laravel-latte
```

4\. Set `'migration_warnings' => true` in `config/latte.php` (by default, it's [enabled for `app.debug`](https://github.com/miloslavkostir/laravel-latte/blob/3.0.x/config/latte.php#L116)). Check your views and resolve the warnings according to the [documentation](https://latte.nette.org/en/develop#toc-migration-warnings).

###  Health Score

49

—

FairBetter than 94% of packages

Maintenance78

Regular maintenance activity

Popularity28

Limited adoption so far

Community13

Small or concentrated contributor base

Maturity63

Established project with proven stability

 Bus Factor1

Top contributor holds 98.1% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~47 days

Recently: every ~1 days

Total

18

Last Release

61d ago

Major Versions

1.x-dev → 2.0.02024-02-28

2.x-dev → 3.0.02024-03-06

PHP version history (3 changes)1.0.0PHP >=7.4.0

2.0.0PHP >=8.0

3.0.0PHP >=8.2

### Community

Maintainers

![](https://www.gravatar.com/avatar/c5c02f59c86548de7a80a9616a569d4daaaaca07c66ed75505a088988f53dc7e?d=identicon)[miloslavkostir](/maintainers/miloslavkostir)

---

Top Contributors

[![miloslavkostir](https://avatars.githubusercontent.com/u/5463235?v=4)](https://github.com/miloslavkostir "miloslavkostir (52 commits)")[![martinoak](https://avatars.githubusercontent.com/u/49438284?v=4)](https://github.com/martinoak "martinoak (1 commits)")

---

Tags

laraveltemplateviewlatte

###  Code Quality

TestsPHPUnit

Static AnalysisPHPStan

Type Coverage Yes

### Embed Badge

![Health badge](/badges/miko-laravel-latte/health.svg)

```
[![Health](https://phpackages.com/badges/miko-laravel-latte/health.svg)](https://phpackages.com/packages/miko-laravel-latte)
```

###  Alternatives

[moonshine/moonshine

Laravel administration panel

1.3k253.1k81](/packages/moonshine-moonshine)[jenssegers/blade

The standalone version of Laravel's Blade templating engine for use outside of Laravel.

8791.3M114](/packages/jenssegers-blade)[ytake/laravel-smarty

Smarty template engine for Laravel and Lumen

87408.6k](/packages/ytake-laravel-smarty)[hasinhayder/tyro-dashboard

Tyro Dashboard - Beautiful admin dashboard for managing Tyro roles, privileges, users, and settings

5443.8k](/packages/hasinhayder-tyro-dashboard)[leitsch/kirby-blade

Enable Laravel Blade Template Engine for Kirby 4 and Kirby 5

2110.6k](/packages/leitsch-kirby-blade)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)