Weave Code
Menu Bundle Laravel Package
swp/menu-bundle
SWP Menu Bundle offers a flexible way to define, organize, and render menus in Symfony applications. Build menu trees in PHP or configuration, integrate with Twig, and handle active states and access control with minimal setup.
[READ-ONLY] Subtree split of the Superdesk Web Publisher Menu Bundle
Frequently asked questions about Menu Bundle
- Is swp/menu-bundle compatible with Laravel?
- No. swp/menu-bundle is a Symfony bundle: it ships a Bundle subclass, a DI Extension with a configuration tree, compiler passes, Doctrine entities, and Symfony event subscribers, all of which assume a Symfony Kernel and a compiled container. Laravel has no bundle concept, and its container is not compiled the way Symfony's is, so there is no native execution path. Wiring it in would require embedding a Symfony micro-container or forking the bundle.
- Can I install swp/menu-bundle in Laravel 10 or 11?
- Composer installation will fail on version conflicts. The last release is from 2018-06-11 and pins Symfony 3.4/4.x with PHP 7.1–7.3, while Laravel 10/11/12 requires PHP 8.1+ and pins symfony/* at ^6.2/^7.x. You would need replace hacks, --ignore-platform-reqs, or a fork that bumps every constraint, and even then the 2018-era code will not run unmodified on PHP 8.
- What does swp/menu-bundle actually do?
- It provides a structured way to define, organize, and render menu trees in PHP or configuration, including nested items, labels, URLs, and custom attributes, with a template-friendly rendering API. The intent is to keep navigation logic out of views and controllers. In practice it is built for Symfony applications, not Laravel.
- Is swp/menu-bundle still maintained?
- There has been no release since 2018-06-11, roughly seven years, with zero stars and zero dependents on this read-only split. Issues and pull requests route to the SuperdeskWebPublisher monorepo, which has its own roadmap priorities, and there is no security patching or PHP 8 compatibility work. Treat it as abandoned for new projects.
- Does swp/menu-bundle support PHP 8?
- No. The package's constraint set targets PHP 7.1–7.3 and Symfony 3.4/4.x, and its code relies on annotations and deprecated Symfony form and event APIs. Bumping the constraints alone would not make it run; you would need a fork that modernizes nullable-typing assumptions and deprecated calls. For a Laravel app, this is not a viable path.
- What are Laravel alternatives to swp/menu-bundle for menus?
- For Laravel, use Laravel-native options: kalnoy/nestedset for hierarchical ordered models, a small custom adjacency-list or nested-set model, or a maintained Laravel menu package. If your requirement is simply a hierarchical, orderable navigation model, these dominate on compatibility, maintenance, and cost. Reusing Superdesk's menu semantics is only justified if you are actually standardizing on that CMS.
- How do I install swp/menu-bundle?
- You would run composer require swp/menu-bundle, but note this is a read-only subtree split of SuperdeskWebPublisher/SWPMenuBundle, not a standalone Laravel package. It is only plausible inside a Symfony application on the matching old Symfony and PHP versions, and even there you should check whether the monorepo's current bundle is materially newer. For Laravel, installation is not recommended and will likely fail dependency resolution.
- Can I use swp/menu-bundle with Blade instead of Twig?
- Not meaningfully. The bundle's Twig integration is a Symfony Twig extension wired through the DI container, routing, and translation services. Laravel uses Blade by default, and adding Twig does not give you Symfony's container or bundle bootstrapping. You would be reimplementing the rendering layer rather than reusing it.
- How long does it take to port swp/menu-bundle to Laravel?
- A fork-and-port is typically a 3–6 engineer-week project plus permanent maintenance, because you must either host the bundle in an embedded Symfony micro-container or rewrite it as a Laravel service provider and reimplement the domain model. A from-scratch menu model for a Laravel app is usually 3–5 engineer-days. The cost of porting dwarfs the value of a menu tree.
- What license does swp/menu-bundle use?
- The provided context does not confirm the license, so check the LICENSE file in the SuperdeskWebPublisher monorepo before using any code. Superdesk Web Publisher projects have historically used copyleft AGPL/GPL-family licenses, which can affect linking into a proprietary product. Confirm licensing and IP constraints before reading the code into your codebase.
Weaver
How can I help you explore Laravel packages today?