README

Inject HTML comments and attributes into compiled Blade templates to expose view file paths and source line numbers. Useful for debugging, IDE integration (e.g. Wisra), and AI/LLM-assisted development.

Installation

Install via Composer:

composer require bardh78/laravel-wisra

The package auto-discovers its service provider. No additional setup required.

Configuration (optional)

Publish the config file to customize behavior:

php artisan vendor:publish --tag=config

Or publish only this package's config:

php artisan vendor:publish --provider="Bardh78\LaravelWisra\LaravelWisraServiceProvider"

Environment variables:

Variable	Default	Description
`LARAVEL_WISRA_ENABLED`	`true`	Enable or disable the instrumentation
`LARAVEL_WISRA_LOCAL_ONLY`	`true`	Only run in the local environment
`LARAVEL_WISRA_SKIP_LIVEWIRE`	`true`	Skip instrumentation for Livewire views and update requests
`LARAVEL_WISRA_INJECT_CONTEXT_META_TAGS`	`true`	Inject request-level Wisra meta tags into the document `<head>`

Note: After enabling or disabling Wisra, clear the compiled view cache so changes take effect:
php artisan view:clear

What it does

View path comments — Wraps each compiled view with  and 
Line annotations — Adds wisra-start-line and wisra-end-line attributes to HTML elements for source mapping
Translation comments — Wraps __() and trans() echoes with  for easier translation debugging

How LLMs benefit from it

When AI coding assistants (Cursor, Copilot, Claude, etc.) work with your Laravel app, they often need to:

Inspect rendered output — Via browser tools, DOM snapshots, or page source
Map HTML back to source — Find which Blade file and line produced a given element
Suggest precise edits — Know exactly where to change code

Without Laravel Wisra: The assistant sees raw HTML with no trace to the Blade source. It must guess files, search the codebase, or rely on structure alone.

With Laravel Wisra: The rendered HTML includes:

Exact file paths in comments, so the assistant knows which view file to edit
Line numbers on elements via wisra-start-line and wisra-end-line, so it can target the correct line
Translation file paths for __() calls, so it can update the right lang file

Example

Rendered HTML with Wisra:

<!-- [view] /project/resources/views/welcome.blade.php -->
<div class="hero" wisra-start-line="5" wisra-end-line="12">
  <!-- [laravel-translation] /project/lang/en/welcome.php -->
  <h1>Welcome to our app</h1>
  <!-- [/laravel-translation] -->
</div>
<!-- [/view] /project/resources/views/welcome.blade.php -->

An LLM can now:

Open resources/views/welcome.blade.php and edit around lines 5–12
Open lang/en/welcome.php to change the translation for the heading
Avoid searching or guessing which files to modify

Best practices for LLM workflows

Enable in local/dev — Keep local_only true so production HTML stays clean
Use with browser MCP tools — When the assistant inspects the page, it gets file/line hints
Combine with Cursor rules — Mention that view comments are present so the assistant knows to use them

Livewire compatibility

Laravel Wisra skips instrumentation for Livewire by default:

Livewire update requests are ignored so Wisra doesn't alter Livewire's AJAX payload rendering
Views in resources/views/livewire/... are ignored
Templates containing Livewire syntax like @livewire, <livewire:...>, wire:*, or $wire are ignored

If you intentionally want Wisra annotations inside Livewire-rendered Blade, set LARAVEL_WISRA_SKIP_LIVEWIRE=false.

Request context meta tags

When a Blade document contains a <head> tag, Wisra can inject request-level meta tags like:

<meta name="wisra-current-route" content="/app/panel">
<meta name="wisra-current-route-name" content="panel.index">
<meta name="wisra-current-controller" content="App\Http\Controllers\PanelController">
<meta name="wisra-current-action" content="index">

These values are rendered at runtime, so they stay correct even when Blade views are cached.

Requirements

PHP 8.2+
Laravel 10.x, 11.x, or 12.x

License

MIT

bardh78 / laravel-wisra

Maintainers

Package info

Statistics

Security