Weave Code
Mjr Box Select Bundle Laravel Package
melk/mjr-box-select-bundle
A PHP bundle that adds reusable box-selection UI components to Laravel applications, letting developers render grouped, selectable boxes for forms and filters with minimal configuration. Includes flexible markup, styling hooks, and simple integration for quick setup.
Ext.ux.form.field.BoxSelect integration with MJR
Frequently asked questions about Mjr Box Select Bundle
- Is melk/mjr-box-select-bundle a Laravel package?
- No. Despite the name, melk/mjr-box-select-bundle is a Symfony bundle for MJR, not a Laravel package. It has no Laravel ServiceProvider, no config publish hook, no Facade, and no Laravel-targeted autoloading. The only reusable part is the vendored Ext.ux.form.field.BoxSelect JavaScript widget.
- Can I install melk/mjr-box-select-bundle with Composer in Laravel?
- Composer installation is not a realistic path for a Laravel app. The package targets Symfony 2.x/3.x-era constraints, so resolution will likely fail against modern Symfony and is meaningless against Laravel. You can require it into a scratch project to inspect files, but do not expect it to boot in Laravel.
- What Laravel versions does this package support?
- None. There is no declared Laravel version support because the package is not built for Laravel. Its Composer constraints point to legacy Symfony, not illuminate components. Treat any Laravel compatibility claim as unverified.
- How do I integrate Ext.ux.form.field.BoxSelect into a Laravel Blade form?
- Do not try to use the PHP bundle. Vendor the Ext.ux.form.field.BoxSelect JavaScript file into resources/js, load it through Vite or Mix, and initialize it only if your page already runs a compatible ExtJS runtime. In a normal Blade page, consider a modern tag or multi-select library instead.
- Do I need a Sencha ExtJS license to use this package?
- Yes, licensing gates adoption. ExtJS is Sencha-licensed under GPLv3 or a commercial license, so you must confirm which applies before any spike. Resolve this in writing before integrating the widget into a Laravel admin UI.
- What are the best Laravel alternatives for tag and multi-select box UI?
- Tom Select, Select2, and Choices.js are maintained alternatives that deliver tag and multi-select box UX without ExtJS. They integrate with Blade, Livewire, Alpine, and Vite in a few lines of JavaScript. For Laravel admin filters, these are the lower-risk choice.
- Does this package work with Livewire, Alpine.js, or Inertia?
- Poorly, if at all. ExtJS owns its own class system, component lifecycle, and DOM, so it will not compose naturally with Livewire round-trips or Alpine reactivity. Isolate it as an iframe-grade boundary only if ExtJS is already the house standard.
- Is melk/mjr-box-select-bundle maintained and safe for production?
- Treat it as an abandoned single-author utility: zero stars, zero dependents, no release cadence, and no visible CI or test suite. That is tolerable for a decorative widget and not for anything load-bearing. Production use requires a fork owner, a maintenance budget, and a license decision.
- How would I port this Symfony bundle to a Laravel ServiceProvider?
- Fork the bundle, replace the Symfony bundle class with a Laravel ServiceProvider, publish the JavaScript asset, and register the field definition. That is tractable but non-trivial, and you still inherit the ExtJS dependency and licensing constraint. In most Laravel apps, skipping the PHP wrapper and vendoring the JavaScript directly is cleaner.
- What should I check before adding this package to a Laravel app?
- Confirm the target admin UI actually uses ExtJS, resolve the Sencha license, and verify the exact ExtJS major version the widget needs. Check whether the requirement is BoxSelect specifically or just a tag and multi-select pattern. If ExtJS is not already standard, keep this package out of the dependency graph.
Weaver
How can I help you explore Laravel packages today?