founderz/laravel-debug-view-names
| Install | |
|---|---|
composer require founderz/laravel-debug-view-names |
|
| Latest Version: | v1.4 |
| License: | MIT |
| Last Updated: | Aug 22, 2026 |
| Links: | GitHub · Packagist |
laravel-debug-view-names
Automatically add comments to indicate where a view starts and ends in rendered HTML in development mode.
Works for any rendered view: it will apply to the root view, @included subviews, and components, at any level of nesting.
Considering this Blade component at resources/views/components/container.blade.php:
<div class="container">
<x-header />
<x-main />
<x-footer />
</div>
The rendered output will be the following, with comments indicating where each component/view starts and ends:
<!-- Starting resources/views/components/container.blade.php -->
<div class="container">
<!-- Starting resources/views/components/header.blade.php -->
<header>
<!-- ... -->
</header>
<!-- Ending resources/views/components/header.blade.php -->
<!-- Starting resources/views/components/main.blade.php -->
<main>
<!-- ... -->
</main>
<!-- Ending resources/views/components/main.blade.php -->
<!-- Starting resources/views/components/footer.blade.php -->
<footer>
<!-- ... -->
</footer>
<!-- Ending resources/views/components/footer.blade.php -->
</div>
<!-- Ending resources/views/components/container.blade.php -->
Installation
You can install this package through composer:
composer require founderz/laravel-debug-view-names
Limitations
The wrapping comments are emitted around every rendered view, including views
rendered inside <script> or <style> tags and views used as JSON, XML or
plain-text responses (e.g. emails, API payloads). HTML comments are not valid
in those contexts and can break the output. The package only activates in the
configured environments (default: local) precisely so this can't reach
production — keep that list narrow.
Related Packages
Laravel Themes: Asset & Views folder per theme. Theme inheritance. Blade integra...