Symfony Profiler Markdown Bundle Laravel Package

Getting Started

This is a Symfony bundle, not a Laravel package — the tourze/symfony-profiler-markdown-bundle name is literal: it plugs a Markdown renderer/collector into the Symfony Web Profiler. If you live in Laravel, this is only relevant when you're working inside a Symfony app (or a Laravel package that bridges into one).

• Install with composer require --dev tourze/symfony-profiler-markdown-bundle (profiler bundles are almost always dev-only).
• First place to look is composer.json in the repo for the required Symfony version, then src/ for the *Bundle.php class and any Resources/config/services.yaml / config/ files that register the collector or Twig template.
• Register the bundle in config/bundles.php (Symfony Flex should do this automatically for the dev env).
• First use case: open the profiler for a request that returns Markdown (e.g. a controller returning text/markdown), and check whether a new profiler panel appears showing the rendered/preview content.

Because 0.0.2 shipped with only a changelog link and no release notes, treat the package as pre-1.0 and undocumented — read the source before trusting behavior.

Implementation Patterns

• Profiler panel workflow: the bundle's value is in dev — boot an app, hit a route, then inspect the panel in /app_dev.php (legacy Symfony) or /_profiler (Symfony 4+). Use it as a debug aid for Markdown-producing endpoints.
• Collector-based integration: if the bundle exposes a DataCollector, you can attach it to your own controllers/services by tagging them, giving you a per-request view of the Markdown payload rather than dumping to logs.
• Twig template override: override the bundle's template via templates/bundles/<BundleName>/... so the rendered Markdown matches your app's styling; this is the standard Symfony bundle pattern and is the cleanest extension point.
• Env-scoped registration: keep the bundle in config/bundles.php under ['dev' => true, 'test' => true] so it never runs in production and doesn't load Twig extensions you don't need.
• Laravel-adjacent tip: if you're building Laravel packages that must render Markdown for docs/API responses, use this as a reference implementation for how Markdown is parsed (look at which library it pulls in — likely league/commonmark or erusev/parsedown) but don't depend on the bundle itself in a Laravel app.

Gotchas and Tips

• It's a Symfony bundle, not Laravel. Do not try to composer require it into a Laravel app expecting a service provider or a Telescope integration — it will install, but nothing will wire it up.
• Skeleton-level release signal. A 0.0.2 with an empty changelog is a strong hint that 0.0.1 → 0.0.2 was housekeeping (CI, README, version bump). Pin to an exact version ("tourze/symfony-profiler-markdown-bundle": "0.0.2") until tagged releases start carrying real notes.
• Dev-only autoloading. Confirm require-dev vs require in the bundle's own composer.json. If it declares symfony/web-profiler-bundle under require, you may get it pulled into production — check with composer why.
• Flex recipe may not exist. Tourze bundles typically rely on manual bundle registration; if config/bundles.php isn't updated, the panel silently won't appear. Verify with bin/console debug:container | grep -i markdown.
• Asset/Twig not built. Many early-stage bundles assume symfony/asset and a working webpack-encore/asset-mapper setup; if the panel loads but is unstyled, you're missing an asset dump.
• Debugging the collector: use bin/console debug:event-dispatcher and check kernel.response listeners — profiler collectors fail quietly. If the panel is empty, dump() inside the collector's collect() method first.
• Version compatibility: 0.0.x bundles frequently lag behind Symfony 6/7 AbstractBundle conventions. If you're on Symfony 7 and the bundle uses Bundle instead of AbstractBundle, you'll see deprecation noise but it should still work — file an issue rather than patching vendor.