Weave Code
Filament Tree View Laravel Package
cube-agency/filament-tree-view
Add a tree view to Filament admin panels. cube-agency/filament-tree-view displays hierarchical records with expandable nodes, making categories, menus, folders, and other nested data easier to browse and manage in Laravel apps.
At a glance
Frequently asked questions about Filament Tree View
- What is cube-agency/filament-tree-view used for?
- It adds a tree view to Filament admin panels so hierarchical records display as expandable, collapsible nodes. Typical uses are categories, navigation menus, folders, and any self-referencing parent/child data that is awkward to browse in a flat table. It is a Laravel package installed through Composer and registered inside your Filament panel.
- Does filament-tree-view support Filament 5 and Laravel 13?
- Yes. The v3.0.0 release notes explicitly state Filament 5 and Laravel 13 support. If your applications are still on Filament 4 or Laravel 12, v3.0.0 will not resolve and you would need the older v2.x line. Confirm the exact constraints in the package composer.json before planning an upgrade.
- How do I install cube-agency/filament-tree-view?
- Install it with Composer using composer require cube-agency/filament-tree-view, then follow the Filament plugin registration steps in the README. The assessment context does not include the full install instructions, so check the repository README for the current panel registration and any asset or config publishing commands. Run composer why-not first if you are unsure your Filament version matches.
- Is there an upgrade guide from v2 to v3 of filament-tree-view?
- The v3.0.0 release notes do not include a migration guide, deprecation list, or UPGRADING.md reference, even though a major version bump signals breaking changes. Until the maintainer documents what changed, any migration estimate is guesswork. Check the repository and issue tracker, and timebox a spike upgrade to size the work in your own code.
- What do the tests cover in filament-tree-view?
- The release notes only say some tests were added, which is neither a coverage figure nor a statement of what is exercised. It is unclear whether they are unit tests only or run against a real Filament panel. Review the CI configuration and test files before treating the package as production-ready for a major release.
- Will filament-tree-view conflict with my other Filament plugins?
- Possibly. A package pinned to the newest Filament major can force every other Filament plugin in your stack forward in lockstep, turning one install into a coordinated multi-vendor upgrade. Run a Composer update dry run or composer why-not filament/filament to see whether the constraint set conflicts with your existing plugins before committing.
- Is filament-tree-view safe to use in production?
- That depends on factors the release notes do not answer, including maintainer responsiveness, commit cadence, and whether v2.x still receives security fixes. The prompt shipping of Filament 5 and Laravel 13 support is a good signal that the maintainer tracks framework currency. Treat adoption as provisional until you review the issue history, support policy, and test coverage.
- Does filament-tree-view ship migrations, config files, or published assets?
- The provided context does not confirm this. Most Filament plugins publish a config file or register assets through a service provider, and some ship migrations, so check the README for vendor:publish tags and whether those artifacts need separate upgrade steps. This matters if you plan to run different package versions across multiple applications.
- What are the alternatives to using a tree view package in Filament?
- You can build a custom Filament page or table around recursive Eloquent relationships, or use another Filament tree plugin. The key question is whether filament-tree-view is a thin wrapper over Filament primitives, which is low lock-in, or whether it adds its own persistence layer, which is high lock-in. Establish that architecture before adopting it across your admin panels.
- Is cube-agency/filament-tree-view actively maintained?
- The v3.0.0 release supporting Filament 5 and Laravel 13 shows the maintainer is tracking framework major versions rather than letting the package lag. However, maintainer identity, commit frequency, and issue response times are not included in the supplied assessment and should be verified on the GitHub repository. Also confirm whether v2.x remains maintained for applications that cannot yet upgrade.
Weaver
How can I help you explore Laravel packages today?