Weave Code
Llms Txt Bundle Laravel Package
silarhi/llms-txt-bundle
A Symfony bundle that automatically generates an llms.txt file for your site, exposing a clean, markdown-based index of your key pages and documentation so large language models can discover and understand your content.
Build, dump and serve an llms.txt file from your Symfony application, the PrestaSitemapBundle way.
Frequently asked questions about Llms Txt Bundle
- Does silarhi/llms-txt-bundle work with Laravel?
- No. It is a Symfony bundle built around the Symfony kernel, container compilation, and Twig functions such as preload() and link(), and it ships no service provider, publishable config, or Artisan command, so it cannot be installed into a Laravel application. Laravel teams should treat it as a reference design and reproduce the behaviour with a small route plus controller, or an Artisan command that writes a static llms.txt file.
- How do I install and configure silarhi/llms-txt-bundle in a Symfony application?
- Install it with composer require silarhi/llms-txt-bundle and confirm the bundle is registered in config/bundles.php for the environments you need. The bundle exposes a built-in route for /llms.txt, so no custom routing or response logic is required. Content, links, and sections are configured through the bundle configuration, and the defaults are enough for a first smoke test.
- Which Symfony versions does version 1.3.0 support?
- The 1.3.0 release notes do not state supported Symfony versions, so check the composer.json constraints in the repository before planning an upgrade. If your application runs an older Symfony LTS, verify that the framework-bundle and routing constraints resolve before committing to the change. Pin the package version in CI so an untested constraint widening cannot slip in unnoticed.
- Why did symfony/web-link become optional in 1.3.0 and will my app break?
- Only the discovery.link_header option needs symfony/web-link, and that option is off by default, so the dependency was demoted to optional. This is a de facto breaking change for anyone who enables link_header without declaring the package (the container build fails) and for anyone whose app or another dependency calls preload(), link(), or AbstractController::addLink() while relying on the bundle's transitive pull of web-link (app boot fails). If either applies to you, add an explicit composer require symfony/web-link before upgrading, then clear and rebuild the cache.
- How does the route caching added in 1.3.0 affect performance?
- Routes carrying the llms_txt option are now cached to %kernel.build_dir%/llms_txt_routes.php alongside compiled routes and invalidated with them. Reported gains are roughly 15.9 ms down to 1.8 ms at 1,000 routes and 720 ms down to 19 ms at 10,000 routes. That removes a real per-request cost cliff that grows with your route count.
- Do I need to run cache:warmup during deployment?
- Yes, if your build directory is read-only, because read-only build dirs are supported only when cache:warmup runs during the build. Skipping warmup, or pointing at an unwritable build dir, can leave the llms_txt_routes.php artifact missing or stale. Treat cache:warmup as a pipeline ordering requirement rather than an optional step, and verify build-dir permissions on every deploy target.
- Why does /llms.txt return a 500 after deployment when the rest of the site works?
- An invalid bundle option fails the requests of the file rather than failing the warmup, so a config typo surfaces as runtime 500s on /llms.txt only, not at deploy time. That weakens a fail-fast posture and can hide the problem until an LLM crawler or uptime check hits the endpoint. Add a post-deploy smoke test that requests /llms.txt, asserts a 200, and validates the expected sections.
- How should I test llms.txt output before and after upgrading?
- In staging, diff the /llms.txt output byte-for-byte against your 1.2.0 baseline so any content or ordering change is deliberate. Capture /llms.txt latency pre- and post-upgrade at your real route count to confirm the new caching actually applies in your environment. A functional test asserting status and expected section headings protects you against future config regressions.
- Is there a Laravel alternative to this bundle?
- There is no Laravel port, and the caching mechanism is kernel-specific with no Laravel analogue. A thin custom route and controller, or an Artisan command that writes a static llms.txt during deploy, reproduces the user-visible behaviour with far less coupling. You would need your own invalidation hook tied to route:cache, and you would not inherit the benchmark gains reported for the Symfony implementation.
- What are the maintenance and upgrade risks of silarhi/llms-txt-bundle?
- The main risks are the quiet demotion of symfony/web-link, stale cache when a pipeline skips warmup or has an unwritable build dir, and config errors that only appear at runtime on /llms.txt. On the positive side, the new cache artifact shares the compiled-routes lifecycle and invalidation, so it cannot drift independently of routes in normal operation. Before upgrading, inventory whether link_header is enabled and whether any code path calls WebLink APIs, declare symfony/web-link explicitly where needed, and upgrade in staging first.
Weaver
How can I help you explore Laravel packages today?