Weave Code
Archetype Bundle Laravel Package
sylius/archetype-bundle
Sylius ArchetypeBundle adds reusable archetypes to Sylius, letting you define product templates with shared attributes and options. It streamlines catalog setup, keeps similar products consistent, and reduces repetitive configuration when creating new items.
[READ-ONLY] Sylius Archetype system bundle.
Frequently asked questions about Archetype Bundle
- What does sylius/archetype-bundle do?
- It adds reusable product archetypes to Sylius so editors can define product templates with shared attributes and options. The goal is to streamline catalog setup, keep similar products consistent, and reduce repetitive configuration when creating new items. It is a Sylius/Symfony domain bundle, not a general Laravel package.
- Can I install sylius/archetype-bundle in a Laravel application?
- No, it should not be used as a runtime dependency in Laravel. It is built on the Symfony DI container, compiler passes, Doctrine ORM mappings, and Sylius ResourceBundle conventions. Laravel's container, Eloquent, and package discovery model are structurally incompatible, so there is no adapter path short of a rewrite.
- Does sylius/archetype-bundle support Laravel 10 or Laravel 11?
- No Laravel version is supported. The package targets legacy Symfony and PHP constraints and is archived read-only. Expect conflicts with modern laravel/framework, doctrine/dbal, and PHP 8.x runtimes. It is not intended for Laravel applications.
- Is sylius/archetype-bundle still maintained?
- No, the repository is archived and read-only with zero dependents. There are no security patches, no PHP 8 or modern Symfony support, and no upstream fixes. The archetype capability was absorbed into Sylius core, so adopting the standalone bundle re-introduces a dependency the vendor deliberately removed.
- What are Laravel alternatives for reusable product templates or archetypes?
- There is no drop-in Laravel package equivalent. Build the concept natively with Eloquent: a product_archetypes table, pivot tables for archetype-to-attribute and archetype-to-option assignments, and a service that hydrates the product-creation form with preselected values. This is a small, well-bounded Laravel feature with clear tests.
- How would I implement product archetypes natively in Laravel?
- Create a product_archetypes model plus pivot tables for archetype attributes and options. Add a service or action that loads an archetype and preselects its attributes and options when a new product is created. Validate the assignments and cover the hydration behavior with feature tests. Do not wrap or fork the Sylius bundle for this.
- Why does Composer resolve sylius/archetype-bundle but the app fails to boot?
- Composer dependency resolution does not guarantee framework compatibility. The bundle expects a Symfony kernel, Symfony DI compiler passes, Doctrine mappings, and Sylius core bundles that Laravel does not provide. It may install at the Composer level but will fail when the framework tries to boot it. Keep it out of a Laravel composer.json.
- Can I use sylius/archetype-bundle with modern Sylius?
- It is not recommended. Archetype-style behavior was absorbed into Sylius core, including product option handling that generates product variant sets. The standalone bundle targets legacy Sylius and Symfony versions and re-introduces a dependency removed from the vendor stack. For a Sylius estate, use the supported core functionality instead.
- What are the risks of forking an archived Sylius bundle for Laravel or legacy projects?
- You take ownership of every bug, compatibility break, and security issue because there is no upstream maintenance. A fork needs a named owner, a patch cadence, and a documented exit timeline from day one. Without that, it becomes an orphaned dependency. For Laravel, reimplement the concept; for legacy Sylius, upgrade to a supported release.
- How do I evaluate whether I need product archetypes at all?
- Validate the requirement separately from package-search relevance. Confirm whether editors genuinely need reusable product templates, or whether the need is for bundles, kits, or made-to-order configurators with arbitrary attribute pricing. Inventory the estate to see whether any legacy Sylius code references archetypes. If Laravel is the target, write a one-page domain spec and build it internally with tests.
Weaver
How can I help you explore Laravel packages today?