- Is fw/last-bundle compatible with Laravel?
- No. fw/last-bundle is a Symfony 4 bundle, not a Laravel package. It relies on Symfony's Kernel, FrameworkBundle, dependency-injection extensions, and bundle registration in config/bundles.php, none of which Laravel boots. Laravel uses service providers and its own container, so the bundle cannot be installed and used as-is in a Laravel application.
- How do I install and configure fw/last-bundle?
- On a Symfony 4 project you would require the bundle with Composer and register it in config/bundles.php, which is the zero-configuration setup it targets. In a Laravel project, Composer will likely fail dependency resolution because the package pins Symfony 4 and PHP 7.1–7.4 constraints. Even if it installs, there is no Symfony kernel to register the bundle, so there is nothing meaningful to configure.
- What does fw/last-bundle actually do?
- It is a zero-configuration static site generator for Symfony projects. LAST crawls your application's URLs, renders each route, and writes the resulting HTML to disk so you can serve static files. The crawl-then-write idea is framework-agnostic in spirit, but the implementation is tightly coupled to Symfony 4's bundle system.
- Which Symfony and PHP versions does fw/last-bundle support?
- The bundle targets Symfony 4 and the PHP 7.1–7.4 era. Symfony 4.4 reached end of security support in November 2023, and there is no PHP 8.1, 8.2, or 8.3 compatibility. There is no version line that matches a modern Laravel 10 or 11 stack.
- Is fw/last-bundle still maintained?
- No. The last release was on 2018-08-31, the repository has around 11 stars and zero dependents, and there is no maintainer activity. That means no security patches, no PHP upgrades, and no ecosystem fixes. Adopting it means owning 100% of the maintenance.
- What are the best Laravel alternatives to fw/last-bundle for static site generation?
- For Laravel, look at spatie/laravel-export for exporting routes to static HTML, or Tighten Jigsaw if you are building standalone docs or marketing sites. For a minimal custom approach, a small Artisan command using the Http facade and Storage can crawl registered routes and write static files. These options avoid Symfony kernel coupling entirely.
- How do I test a static site export in Laravel?
- If you build a Laravel-native exporter, test the Artisan command with Http::fake() and Storage::fake('static'), then assert that the expected files and routes were written. You cannot meaningfully test fw/last-bundle in a Laravel test suite because the Symfony bundle never boots. Treat the export output as a snapshot artifact and compare it in CI.
- Can fw/last-bundle improve SEO or TTFB for my Laravel site?
- Static export can help SEO and TTFB in principle, but fw/last-bundle cannot run on Laravel, so it cannot deliver those benefits there. For most Laravel apps, HTTP caching and a CDN solve the same latency problem with far less risk. If you truly need static output, use a Laravel-native exporter instead.
- Does fw/last-bundle work on PHP 8?
- No. The package is from the PHP 7.1–7.4 era and has no PHP 8.x compatibility updates. Running it on PHP 8.1 or later is unsupported and likely to fail on dependency constraints or deprecated Symfony 4 code. You would need to fork and modernize it, which is effectively a rewrite.
- Should I fork fw/last-bundle to add Laravel support?
- Forking is possible but not recommended as a first move. Decoupling the Symfony kernel, DI extension, compiler passes, and command registration for Laravel is a port rather than an integration, with an ongoing maintenance burden. Mine the repository only as a reference for crawl and incremental-build ideas, and build a thin Laravel-native exporter instead.