Weave Code
Web Bundle Laravel Package
sylius/web-bundle
Sylius WebBundle provides the web layer for Sylius e-commerce applications, integrating controllers, templates, routing, and UI components for storefront and admin interfaces. It helps developers build and customize Symfony-based shop frontends and backends.
DEPRACATED. See Sylius/Sylius repository.
Frequently asked questions about Web Bundle
- Can I use sylius/web-bundle in a Laravel application?
- No. It is a Symfony bundle that depends on Symfony's bundle registry, kernel and compiler-pass lifecycle, and Sylius domain primitives such as resource configuration, Doctrine mappings, grids, and state machines. Laravel has no bundle attachment point, so there is no supported integration path. The repository is archived and deprecated, so even on Symfony you should use sylius/sylius instead.
- Is sylius/web-bundle still maintained?
- No. The GitHub repository is archived and explicitly deprecated, and the description redirects users to Sylius/Sylius. Development was consolidated into the Sylius monorepo, so this package is a historical artifact rather than a maintained distribution channel. It has no active security response or compatibility work as PHP and Symfony majors advance.
- What Laravel versions does sylius/web-bundle support?
- None. The package is built for Symfony and Sylius applications and does not declare Laravel framework support or provide Laravel service providers, facades, or Eloquent integration. A Laravel application cannot load it through the normal package discovery mechanism. For Laravel commerce needs, evaluate Laravel-native or headless alternatives instead.
- How do I install sylius/web-bundle?
- In a legacy Symfony and Sylius application it would be installed with Composer and registered in the Symfony kernel, but that path is obsolete because the code now lives in sylius/sylius. For current Sylius projects, require sylius/sylius and consume the equivalent web-layer code from the monorepo. Do not add this archived package to a new Laravel or Symfony project.
- What should I use instead of sylius/web-bundle for a Laravel storefront?
- The right choice depends on whether you need a full commerce platform, a headless commerce service, or a narrow capability such as catalog routing or admin scaffolding. Laravel-native commerce packages and headless commerce APIs are the realistic options; a Symfony bundle is not. Define the capability requirement first, then compare 24-month total cost of ownership, maintenance, and security response. Avoid forking an abandoned bundle to get there.
- Does sylius/web-bundle work with Eloquent or Laravel Blade?
- No. It ships Twig templates, Symfony controllers and routes, and assumes Sylius resource configuration and Doctrine ORM mappings. Laravel's Eloquent and Blade are not part of its design, and there is no adapter layer in the package. Recreating the Sylius domain model inside Laravel would be a platform decision, not an integration task.
- Is sylius/web-bundle safe to use in production?
- No, not for a new or maintained production system. The package is archived with no maintainer, so there is no CVE triage, no security response, and no compatibility work as PHP and Symfony versions advance. Its pinned Composer constraints can eventually collide with modern dependencies and leave the lockfile owner unable to upgrade or remove it cheaply. Shipping it also concentrates maintenance knowledge in people who know Symfony bundle mechanics and the Sylius domain model.
- What is the difference between sylius/web-bundle and sylius/sylius?
- sylius/web-bundle was the standalone Symfony bundle providing the web-facing layer, including controllers, routing, Twig templates, and UI assets. Its development was consolidated into the Sylius monorepo, and the standalone repository is archived and deprecated. Current Sylius applications should depend on sylius/sylius and take the equivalent web-layer code from there. The standalone package is a historical artifact, not a supported distribution channel.
- Can I fork sylius/web-bundle and maintain it myself?
- Forking is technically possible but strategically indefensible for most teams. You would inherit an abandoned codebase that requires Symfony bundle and Sylius domain expertise to maintain, plus ongoing security and upgrade work with no upstream. You would also need a named owner who is accountable indefinitely, creating a single point of failure on a revenue-adjacent surface. If you already run Sylius, upgrade within the monorepo instead; if you run Laravel, build or buy the narrow capability natively.
- Does sylius/web-bundle provide admin and storefront UI out of the box?
- It provides Symfony and Sylius web-layer pieces such as controllers, routes, Twig templates, layout partials, and UI assets for storefront and admin interfaces. It is not a drop-in UI for Laravel, and much of it is thin glue over Sylius core rather than standalone functionality. Without Sylius resource configuration, Doctrine mappings, grids, and state machines, those templates and controllers have no working domain behind them. For a Laravel admin or storefront, use Laravel-native tooling or a headless commerce frontend.
Weaver
How can I help you explore Laravel packages today?