Weave Code
Select Laravel Package
laravel-enso/select
Select component for Laravel Enso, pairing a Vue frontend with backend support for searchable, server-side option loading. Integrates with Enso forms and the broader ecosystem for building dynamic, ajax-powered dropdowns.
Bulma styled single and multi-select component with a server-side option list builder
Frequently asked questions about Select
- What is laravel-enso/select used for?
- laravel-enso/select is a select component for the Laravel Enso admin framework. It pairs a Vue frontend styled with Bulma with a server-side option list builder, so you can render single and multi-select dropdowns whose options are loaded from the backend. It is a leaf component of Enso rather than a general-purpose Laravel package.
- Can I use laravel-enso/select outside a Laravel Enso application?
- It is possible but conditional. The package is built as a leaf component of Laravel Enso, and its server-side builder almost certainly extends Enso base classes and conventions. Outside Enso, you would be adopting a component that assumes a host framework you do not have, so treat it as a reference implementation rather than a drop-in dependency.
- Which PHP, Laravel, and Vue versions does laravel-enso/select support?
- You need to check composer.json and the release history, because the available context does not pin exact versions. Enso's lineage is Vue 2, which is end-of-life, and the package also depends on Bulma for styling. Before committing, record the full matrix of PHP, Laravel, Enso, Vue, and Bulma versions your application uses.
- Does laravel-enso/select support Vue 3?
- Enso's lineage is Vue 2, so the package was built for the Vue 2 era, and Vue 2 is end-of-life. Whether a Vue 3 port exists depends on the current Enso release line, and you should verify that directly in the repository. If your frontend is on Vue 3, confirm an Enso Vue 3 line exists and whether this component has been ported before you plan around it.
- Will laravel-enso/select work with Bootstrap or Tailwind CSS?
- No, Bulma is a hard dependency for the component's styling. If your application uses Bootstrap or Tailwind, the Bulma styles will conflict with your design system, and you would need to isolate the component's CSS scope. For non-Bulma stacks, porting the server-side option pattern into your own select component is usually the better route.
- Does the server-side option list builder support search and pagination?
- The package is described as a server-side option list builder for searchable, ajax-powered dropdowns, which is the pattern it exists to support. The available context does not confirm the exact search and pagination semantics, so review the builder's request and response shape before relying on it. If it serializes full option sets, add server-side search and pagination yourself.
- How do I install and configure laravel-enso/select?
- Install it with Composer inside a Laravel Enso application and follow Enso's asset pipeline conventions. Verify whether the package expects Laravel Mix or Vite, because a mismatch turns a drop-in component into a build-config project. For testing, spike it in a throwaway Enso app, render single and multi-select against a large reference table, and measure payload size and latency before wiring it into production.
- Can I use the backend option builder without the Vue select component?
- In principle the two halves are separable, but in practice the builder is Enso-shaped PHP that follows Enso conventions. You can review the builder's contract, including endpoint shape, search and pagination semantics, and option payload, and reimplement it in your own controller and service class. That port is often cheaper to maintain than importing Enso coupling into a non-Enso application.
- Is laravel-enso/select actively maintained and production-ready?
- Maintenance is inherited from the Enso ecosystem rather than from this package alone, and upgrades to Laravel or Vue arrive as Enso major-version events. The package has a thin standalone footprint, so you are likely to be the first to encounter edge cases rather than finding them answered in issues. Inside Enso it is low risk; for standalone production use, pin the compatibility matrix and plan for Vue 2 end-of-life.
- What are the alternatives if I only want the server-side option pattern?
- If you only want the pattern, build a server-side, searchable, paginated option endpoint in your own Laravel controller and service class, then pair it with your existing design-system select. For Enso applications, adopting this package is the natural low-friction choice. For non-Enso applications on Bootstrap, Tailwind, or Vue 3, porting the pattern is usually the better technical call.
Weaver
How can I help you explore Laravel packages today?