- Is tadcka/jstree-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. It registers Tadcka\JsTreeBundle\TadckaJsTreeBundle through the Symfony kernel and relies on Twig helpers and Symfony DI asset registration. Laravel gets no ServiceProvider, facade, Blade views, or publishable config.
- Can I install tadcka/jstree-bundle in Laravel 10 or Laravel 11?
- No supported Laravel version exists. The bundle targets Symfony 2.x and PHP 5.x-era constraints, while Laravel 10 and 11 require modern PHP and Illuminate components. Pulling Symfony framework-bundle into Laravel just to get a tree widget is not a viable integration.
- Does Laravel package auto-discovery register tadcka/jstree-bundle?
- No. Laravel package discovery looks for Illuminate ServiceProviders and extra.laravel metadata. This package exposes a Symfony bundle class and Twig/DI wiring, so discovery will not autoload anything usable in a Laravel application.
- What Laravel and PHP versions does tadcka/jstree-bundle support?
- None for Laravel. Its Composer constraints date to 2015 and target Symfony 2.x with PHP 5.x, so it does not support Laravel 10 or 11 or modern PHP 8.2 and 8.3 runtimes. Any install would require constraint overrides or ignore-platform-reqs, which is unsupported.
- Why does Composer fail to install tadcka/jstree-bundle on PHP 8.2 or 8.3?
- Composer resolution will likely fail because the package's 2015 constraints conflict with modern PHP and Symfony or Illuminate dependency trees. Using --ignore-platform-reqs or constraint overrides only forces installation of unverified code on an unsupported interpreter. That is not a production-safe workaround.
- What is tadcka/jstree-bundle used for, and does it provide server-side tree storage?
- It wraps the client-side jsTree jQuery plugin for Symfony by registering vendor JS and CSS and exposing a Twig-rendered container. It does not provide server-side tree storage, querying, or ordering. If you need hierarchy persistence, use a nested-set or closure-table package in Laravel instead.
- How is tadcka/jstree-bundle configured, and is there a publishable Laravel config?
- Configuration is Symfony DI and Twig based, with no publishable Laravel config file. There is no config/jstree.php, no Blade component, and no Laravel asset publishing. You can read the Twig markup as a reference, but you must rebuild the configuration in Laravel.
- How do I render a hierarchical jsTree in Laravel without this Symfony bundle?
- Install jsTree from npm, import it in resources/js/app.js under Vite, and render a Blade component that outputs the container plus a small Alpine or vanilla init script. Expose nodes through a JSON endpoint, apply a policy for authorization, paginate children, and protect write routes with CSRF. Use kalnoy/nestedset if you need server-side ordering.
- Is tadcka/jstree-bundle maintained, tested, and safe for production?
- It is high risk for production. The last release was 2015-09-25, with 2 stars, 0 dependents, no tests, no CI, and no SECURITY.md. Unmaintained transitive JavaScript is a known vector for silent XSS and prototype-pollution issues, and there is no maintainer response path.
- What are the best alternatives to tadcka/jstree-bundle for tree views and drag-and-drop reordering in Laravel?
- For Laravel, use npm jstree or a modern tree component with a Blade wrapper and JSON endpoint; add kalnoy/nestedset for persisted hierarchy and drag-drop reordering. Effort is roughly 1-2 engineer-days for a read-only tree and 3-5 days for authorized reorder persistence. If jQuery is mandated, vendor jsTree directly from npm rather than installing the Symfony bundle.