- Can I use netgusto/devserver-bundle in a Laravel application?
- No. It is a Symfony bundle built around AppKernel bundle registration, a Symfony configuration tree, and a Symfony console command, none of which exist in Laravel. Laravel registers console commands through Artisan and its service container, so the package cannot be installed or booted in a Laravel app. Treat it as a concept reference only, not a dependency.
- Does netgusto/devserver-bundle support Laravel 10 or 11?
- No. It declares Symfony framework constraints rather than Laravel ones, and its bundle conventions point to PHP 5.x or 7.0-era requirements with Symfony 2 or 3 components. Composer will typically fail on constraint resolution before anything else if you try to require it in a modern Laravel 10 or 11 project. There is no tagged release targeting supported Laravel versions.
- Is there a Laravel equivalent to netgusto/devserver-bundle?
- Yes, Laravel ships or officially recommends native equivalents for every feature the bundle offers. php artisan serve covers the development HTTP server, Laravel Valet or Herd handle wildcard .test subdomains, and Vite handles automatic asset compilation with hot module replacement. Nothing in the bundle's feature set is missing from a current Laravel stack.
- How do I set up wildcard subdomain routing for local Laravel development?
- Use Laravel Valet or Laravel Herd with a parked or linked site, which resolves *.test subdomains automatically without extra configuration. Alternatively, run php artisan serve behind a wildcard DNS entry such as *.lvh.me or a matching hosts file entry. Both approaches avoid introducing an unmaintained third-party dev server into your project.
- How do I install netgusto/devserver-bundle?
- It is installed with Composer into a Symfony application, then enabled in AppKernel and configured through the bundle's configuration tree. There is no Laravel installation path because Laravel has no bundle registration step or AppKernel class. Attempting a Composer require inside a Laravel project will normally fail on dependency constraints first.
- Is netgusto/devserver-bundle still maintained?
- There is no meaningful adoption or maintenance signal: the repository shows zero stars, zero dependents, and no recent commit activity captured in its technical evaluation. The Symfony bundle conventions it uses imply end-of-life PHP and Symfony constraints. If you needed a compatibility fix, forking the code would be your only realistic path.
- Does netgusto/devserver-bundle compile assets automatically?
- It advertises automatic asset compilation, but that approach belongs to the Assetic, Grunt, and Gulp era of build tooling. Depending on the implementation it may be a file watcher or per-request compilation, and the latter adds unpredictable latency to every page load. Modern Laravel uses Vite with hot module replacement, which gives faster feedback and is first-party.
- What are the security concerns of a third-party dev server with subdomain support?
- A dev server that binds to a host interface and honors arbitrary Host headers, which subdomain routing requires, is exactly the class of tool that can enable DNS-rebinding attacks if exposed beyond loopback. Bundles of this vintage often shell out to the PHP built-in server or ship a prebuilt binary, adding an unreviewed executable and a download step on developer machines and CI. Dev-only scope reduces the blast radius but does not remove the risk.
- Can I port the subdomain routing from netgusto/devserver-bundle to Laravel?
- The code is not portable because it depends on Symfony kernel and console APIs, so only the concept carries over. In practice you would replicate the behavior with Valet or Herd parked sites, a wildcard DNS alias, or per-site .test hosts. That is almost always less work than rewriting the bundle against Laravel's container and Artisan.
- What should Laravel developers use instead of netgusto/devserver-bundle for local development?
- Use php artisan serve for a quick built-in server, Laravel Valet or Herd for parked sites and wildcard subdomains, Laravel Sail for containerized environments, and Vite for asset compilation with hot module replacement. All of these are supported, documented, and actively maintained. Adding a Symfony bundle to a Laravel application is never the shorter path.