- How do I install joy/voyager-import in a Laravel app?
- Install it with Composer using composer require joy/voyager-import, then register the package service provider in your Laravel app. Publish any package config if the module offers it, and enable the import action per BREAD resource in the Voyager admin panel. The package is additive, so removing it should restore stock Voyager behaviour, though you should confirm whether it ships migrations or log tables before adopting it.
- Which Laravel and Voyager versions does joy/voyager-import support?
- There is no published compatibility matrix, so treat the composer.json version pins as the only authoritative statement of support. The visible release dates to around February 2024, which means it is unlikely to have been validated against Laravel 11.x or Voyager forks. Check the pins and any CI/test configuration before installing, and plan a version-pin or fork contingency if your stack sits outside that range.
- Does joy/voyager-import work in a Laravel app that does not use Voyager?
- No. This is an admin-plane add-on that extends Voyager's BREAD system, so its value only materialises inside an existing Voyager installation. In a Laravel app that uses something else for back-office CRUD, the architectural fit is effectively zero and the package should be rejected quickly. It complements Voyager rather than replacing it.
- What file formats can joy/voyager-import import — CSV only or XLSX too?
- The blurb only says data is brought in from uploaded files, so the exact format list must be confirmed from the source or composer.json. If a spreadsheet reader such as phpoffice/phpspreadsheet or Laravel Excel is a dependency, XLSX is likely supported alongside CSV. Test with real-world fixtures including mixed encodings and malformed rows, because that is where parsing tends to fail silently.
- Does joy/voyager-import wrap imports in a database transaction, and what happens if row N fails?
- This is not documented, so treat the source code as the specification during your spike. Verify whether the whole import runs inside a single transaction or commits row by row, and record the rollback behaviour when a row fails partway through. Row-level failure handling and partial-import semantics are the highest data-integrity risk with an under-supported package like this.
- Does the import respect Voyager BREAD validation rules and field types?
- Unknown from the documentation, and it matters because bypassing BREAD validation can push bad data past the constraints Voyager enforces on manual edits. Inspect the import handler to see whether it reuses the BREAD field definitions and validation rules or writes directly to the model. Confirm behaviour on required fields, unique keys, and relationship columns before running it against a production table.
- Does joy/voyager-import respect Voyager roles and permissions?
- The package adds an import action to Voyager's admin panel, but whether it honours BREAD-level role and permission gates is not documented. Check whether the import route sits behind Voyager's middleware and permission checks or bypasses them. If it bypasses them, any Voyager admin user could bulk-write to tables they otherwise cannot edit, which is a governance concern worth validating early.
- Can joy/voyager-import update existing records, or is it insert-only?
- Upsert behaviour and duplicate-key policy are not stated in the overview, so verify against the source. Determine whether imports are insert-only, support update-by-key, or fail on duplicate rows, and test each case with a fixture containing duplicates. This directly affects whether the package is safe for syncing data or only for one-off seeding.
- Is import processing synchronous, or can large imports be queued?
- Imports are most likely request-bound and synchronous, which makes large files a timeout and memory risk. Check for any chunk or batch size control and whether processing can be pushed onto a queue. Run a roughly 10k-row fixture during evaluation and measure request time, memory use, and behaviour on failure before committing to it.
- Is joy/voyager-import actively maintained, and what are the alternatives?
- Adoption signals are weak: a single visible maintainer, a handful of stars, no dependents, and a release that is roughly two years old, so assume you will own patches if you adopt it. For higher-traffic needs, evaluate Laravel Excel or a custom BREAD-aware importer that you control. Run a one- to two-day spike against your exact Laravel and Voyager pins before piloting it on a single low-risk entity.