- What is techouse/select-auto-complete and does it work outside Laravel Nova?
- It is a third-party Laravel Nova field that replaces standard select inputs with searchable, auto-completing dropdowns, backed by a PHP Field subclass and a compiled Vue component mounted in the Nova admin SPA. Despite documentation language mentioning Blade-based forms and ordinary select inputs, independent review classifies it as Nova-locked. Treat it as working only inside Laravel Nova until you prove otherwise, and do not assume it functions in Filament, Backpack, Livewire, or hand-rolled Blade forms.
- Which Laravel Nova versions does techouse/select-auto-complete support?
- The repository is archived, so the only reliable answer is whatever laravel/nova constraint appears in its composer.json at archived HEAD. Nova couples third-party fields to both its PHP field API and its front-end contract, with Nova 3 on Vue 2 and Nova 4/5 on Vue 3 with Inertia, so cross-major compatibility cannot be assumed. Read that constraint and compare it against the Nova version you actually run before writing any integration code.
- How do I install techouse/select-auto-complete in a Laravel app?
- Installation follows the standard Nova field pattern: run composer require techouse/select-auto-complete, rely on package auto-discovery for the service provider, then add the field to the target Nova resource. The first gate is version alignment rather than the install command itself, because the package is archived and has no fix path across a Nova major upgrade. Verify the Nova constraint first, then freeze the dependency to the release current at archive time.
- Does techouse/select-auto-complete support dependent or cascading select fields?
- Yes, dependent fields are listed among the package's features, alongside AJAX-powered remote options and customizable queries. The exact fluent API for wiring one field to another is not verifiable from the overview alone, so inspect the source to confirm the surface before designing a form around it. Because adoption is essentially zero, dependent-field behavior has effectively only been validated by the original author.
- How does the AJAX search endpoint work and is pagination bounded?
- The package registers a search route that queries options remotely and returns results to the Vue component, which is what makes lists of thousands of options navigable. Whether pagination is bounded, whether result counts are capped, and what index backs the LIKE predicate are all unverified. For large tables, confirm there is a hard result cap and an appropriate index before shipping to production.
- Does the search endpoint respect Nova authorization and tenant scoping?
- This is unverified and is one of the main technical risks flagged in review. The key question is whether the AJAX search handler runs results through Nova's policy layer and confines them to the caller's tenant or model scope, or queries the model directly. Since the package has 30 stars, zero dependents, and is archived, nobody but the original author has exercised this path. Audit the handler yourself before exposing it in a multi-tenant admin panel.
- Is techouse/select-auto-complete still safe to use in production now that the repo is archived?
- Archived status plus negligible adoption is the dominant risk: authorization scoping, pagination, and empty-result handling are validated by nobody but the author. Blast radius is genuinely small because the field touches no domain models or request lifecycle beyond registering a search route, but strategic leverage is small too. The MIT license is the real mitigation, since forking or reimplementing is legally free. Evaluate Nova's native searchable select first, then treat a fork or a few-hundred-line in-house field as the fallback.
- Is there a built-in Nova searchable select that makes this package unnecessary?
- Possibly. Current Nova versions may already cover searchable selects natively, which would mean the package's reason to exist has evaporated. Evaluate the native option first because it carries zero extra dependency and no archive risk. Also confirm that Nova remains a deliberate, funded part of your platform strategy, since Filament ships searchable async selects natively and is a weak argument for staying on Nova.
- Can I fork techouse/select-auto-complete into my own namespace?
- Yes, the MIT license makes forking or reimplementing legally free, so absorbing the pattern costs little beyond engineering time. Vendoring means accepting full ownership, including the compiled dist/js bundle, which you may be unable to rebuild if it has drifted from resources/js. A fork is only justified if the source contains non-obvious behavior you would struggle to reproduce. Reading it as a spec, covering debounced async loading, a searchUsing-style fluent surface, and result caps, is usually enough to build your own.
- Will techouse/select-auto-complete conflict with my other Nova field packages?
- Unknown without testing. The risks are asset-manifest collisions and global component-name clashes when the compiled Vue component mounts alongside other field packages. Because the repo is archived, any conflict you find has no upstream fix path. Build a smoke test that loads your full set of Nova field packages together before committing to the dependency.