Weave Code
Provides commands for running applications using the PHP built-in web server
Frequently asked questions about Web Server Bundle
- Can I use Symfony’s WebServerBundle in a pure Laravel project without conflicts?
- No, this bundle is not optimized for Laravel and risks conflicts with Laravel’s `artisan serve`, route caching, and middleware. It’s only recommended for hybrid Symfony/Laravel projects where Symfony’s Profiler or VarDumper is critical. For pure Laravel, alternatives like `laravel/valet` or `sail` are safer.
- What Laravel versions does symfony/web-server-bundle support?
- The bundle itself doesn’t enforce Laravel version checks, but it’s archived and lacks updates since 2022. Test thoroughly with Laravel 10.x/11.x, as conflicts with route caching or middleware (e.g., VerifyCsrfToken) may arise. No official Laravel-specific optimizations exist.
- How do I install symfony/web-server-bundle in Laravel?
- Run `composer require symfony/web-server-bundle:4.4.44` and configure it in your `config/bundles.php` (Symfony-style). However, this requires a Symfony-compatible project structure. Laravel projects may need manual workarounds for `.env` handling or service container conflicts.
- Is this bundle safe for CI/CD pipelines?
- No, it’s not recommended. The bundle is single-threaded, lacks HTTP/2, and may introduce flaky tests due to environment differences with Laravel’s `artisan serve`. Use `sail` or `valet` for consistent CI/CD setups. Bind to `127.0.0.1` if used, but audit for exposed endpoints.
- Why does Symfony recommend using their new Local Web Server instead?
- The new [Symfony Local Web Server](https://symfony.com/doc/current/setup/symfony_server.html) is actively maintained, supports HTTP/2, and integrates better with modern Symfony workflows. This bundle is deprecated since Symfony 4.4 and lacks updates, making it a higher-risk choice.
- Will this bundle work with PHP 8.3+ or Symfony 7.x?
- Unlikely. The bundle is pinned to Symfony 4.4.44 and hasn’t been updated since 2022. PHP 8.3+ or Symfony 7.x may introduce compatibility issues. Pinning to `4.4.44` is advised, but long-term use risks breaking changes. Consider forking or migrating to alternatives.
- Can I use Symfony’s Profiler or VarDumper with Laravel via this bundle?
- Yes, but it’s optional and not native to Laravel. The bundle integrates Symfony’s debugging tools, but Laravel’s `telescope` or `dd()` may suffice. Profiler integration requires manual configuration and may conflict with Laravel’s service container or middleware.
- What are the performance limitations of this bundle in production?
- This bundle is **not** production-ready. It uses PHP’s built-in server, which is single-threaded, lacks HTTP/2, and lacks performance optimizations. For staging/production, use `php-fpm` + Nginx. Document this explicitly in your team’s setup guidelines.
- Are there alternatives to symfony/web-server-bundle for Laravel?
- Yes. For local development, use `laravel/valet` (macOS/Linux) or `laravel/sail` (Docker-based). Both are actively maintained, Laravel-native, and avoid conflicts. If you need Symfony tools, consider a hybrid project structure or the new Symfony Local Web Server.
- How do I migrate from symfony/web-server-bundle to laravel/valet or sail?
- Replace `php bin/console server:run` with `valet link` (for valet) or `sail up` (for sail). Update your `package.json` scripts to use Laravel’s native tools. Test thoroughly, as middleware or route caching may behave differently. Document the migration timeline to avoid future conflicts.
Weaver
How can I help you explore Laravel packages today?