Weave Code
Webapp Pack Laravel Package
symfony/webapp-pack
Symfony Flex metapackage that installs a curated set of bundles for building full web applications: framework, Twig, Doctrine ORM, security, forms, validator, mailer, console, and Maker. Use it to bootstrap a standard Symfony webapp with a single composer require.
symfony/webapp-pack is a Composer metapackage from Symfony that gives new web applications a curated starting set of dependencies. Installed through Symfony Flex, it brings together common bundles for templating, forms, security, database access, debugging, and developer tooling—so you can start building features instead of assembling packages one by one.
- One-command setup for a full-stack Symfony web app
- Curated dependency set maintained by the Symfony team
- Works with Symfony Flex recipes and configuration
- Sensible defaults for development and debugging
- Contains no application code; it is a metapackage
Frequently asked questions about Webapp Pack
- Can I install symfony/webapp-pack inside a Laravel application?
- No, direct installation in a Laravel app is not recommended. The pack is a Symfony Flex metapackage built to bootstrap a full Symfony application, while Laravel already ships its own skeleton, service container, routing, ORM, and frontend tooling. Adding it would pull broad Symfony framework packages and conventions that can cause dependency-resolution conflicts, duplicated tooling, and confusing ownership. Only consider it for a standalone Symfony service or an approved sidecar app, not your Laravel codebase.
- What does symfony/webapp-pack actually install?
- It is a Composer metapackage, so it ships no runtime application code of its own. It pulls a curated set of recommended Symfony packages, typically including the framework, Doctrine ORM, console, Twig, security, validation, and mailer. The practical effect is that a fresh Symfony skeleton becomes a full-featured web application in one require. Because everything is transitive, you inherit whatever versions and maintenance state those dependencies have.
- Is symfony/webapp-pack a Laravel package or a Symfony package?
- It is a Symfony package. Specifically, it is a Symfony Flex Composer pack intended to be installed on top of the default Symfony skeleton. It has no Laravel-specific integration, service providers, or configuration. Laravel does depend on selected Symfony components internally, but that is a different and much narrower relationship.
- How do I install symfony/webapp-pack and what are the requirements?
- The typical flow is composer create-project symfony/skeleton, followed by composer require symfony/webapp-pack, with Symfony Flex enabled so recipes can configure the new packages. You need a supported PHP version and a Symfony version that the pack's constraints allow. The last tagged release was 2023-12-11, so validate PHP and Symfony version compatibility before committing. Run composer audit immediately after installation.
- Which Laravel and PHP versions does symfony/webapp-pack support?
- There is no meaningful Laravel version support because the pack is not a Laravel package. For PHP and Symfony, check the constraints declared by the metapackage and its transitive dependencies rather than assuming current versions work. Given the December 2023 last release, newer Symfony minors and PHP releases should be verified in a throwaway branch first. Treat any compatibility claim as something you must prove with a real Composer resolve.
- Will symfony/webapp-pack conflict with Laravel's existing Symfony components?
- Conflict risk is real. Laravel consumes a selective set of Symfony components pinned to versions Laravel's own release supports, whereas this pack is designed to shape an entire Symfony application and will pull broader packages and conventions. That can produce Composer resolution conflicts, duplicate framework tooling, and autoload or convention collisions. If you must experiment, do it in an isolated branch and read the full composer why-not output.
- Is symfony/webapp-pack still maintained and safe to use in production?
- Signals are weak: roughly 22 GitHub stars and a last release on 2023-12-11. Because it is a metapackage, the real risk is transitive, including abandoned or vulnerable dependencies, resolution conflicts, and unclear long-term upgrade ownership. Run composer audit, check for abandoned packages, and confirm who owns patching before production use. For many teams, an explicit and auditable composer require list is safer than a low-signal metapackage.
- What are the alternatives to symfony/webapp-pack for a Laravel project?
- For Laravel work, use Laravel-native starters such as laravel/laravel with Breeze or Jetstream, and add individual Composer packages only as needed. For Symfony work, use symfony/skeleton plus an explicit list of the components you actually want. If you like the pack's curation, copy its package list into an internal approved-dependency matrix instead of installing the metapackage. That gives you the same outcome with clearer ownership and auditability.
- How do I test an application bootstrapped with symfony/webapp-pack?
- Use standard Symfony testing: PHPUnit for unit and integration tests, symfony/browser-kit or Panther for functional and end-to-end coverage, and a smoke test that boots the kernel and hits key routes. Add composer audit and a dependency-review step to CI so transitive advisories surface early. Pin the lock file and test upgrades in a branch before merging. Also verify that Flex recipes applied the expected configuration files.
- Can I use symfony/webapp-pack as a reference when choosing packages for Laravel?
- Yes, that is the most sensible use in a Laravel-first estate. Treat the pack as a blueprint and extract its recommended package list into an internal approved-dependency matrix. Do not install it into Laravel just to inherit that list, since Laravel already selects its own Symfony components. Document the decision so future maintainers know why the pack was evaluated and rejected for direct use.
Weaver
How can I help you explore Laravel packages today?