- How do I install tu6ge/voyager-excel in a Laravel app?
- Install the package with Composer and confirm the exact package version in your composer.json. The assessment suggests it is likely installable with Laravel auto-discovery, config publication, and Voyager BREAD export wiring. Check the repository README for the specific install command, config publishing step, and any required Voyager registration. Validate a default BREAD export in a sandbox before rolling it out.
- Does voyager-excel support Laravel 10, Laravel 11, and Voyager 1.x?
- The provided context does not list supported Laravel, Voyager, PHP, or spreadsheet-engine versions. Check the package composer.json and release notes for explicit constraints before installing. Pin package, Laravel, Voyager, PHP, and spreadsheet dependencies, then test against a matrix that matches production. Do not assume compatibility from the package name alone.
- How do I create a custom Excel export format in voyager-excel v2.2.0?
- Version 2.2.0 adds custom export format support, but the provided context does not document whether the API is config-based, class-based, or callback-based. Inspect the repository source, README, and any examples to confirm the registration contract. Start with one low-risk BREAD and validate dates, relations, nulls, and permissions. Document the pattern internally before applying it to additional BREADs.
- Can voyager-excel import Excel files into Voyager BREAD records?
- The package blurb says it adds Excel import and export support to Voyager BREAD, while the short description emphasizes export. Verify import support in the README and the exact version you install before relying on it. If import is supported, test create and update workflows with representative data and rollback behavior. If it is export-only in your version, use a separate import workflow.
- Are voyager-excel exports permission-aware in Voyager?
- Permission awareness is not confirmed by the provided context and is listed as a key question and operational risk. Add explicit authorization checks around export routes or actions and test with multiple Voyager roles. Review the package code or documentation for any built-in permission enforcement. Treat permission leakage as a failure mode to monitor.
- Can large Voyager BREAD exports be chunked or queued with voyager-excel?
- The assessment warns that synchronous Excel exports can exhaust memory or time out on large tables. It does not confirm built-in chunking or queue support, so test representative data volumes and constrain export row counts. Monitor export duration and failure rates, and add queueing or a Laravel Excel fallback if needed. Do not assume large exports are safe without load testing.
- Is tu6ge/voyager-excel actively maintained and safe for production?
- The assessment describes it as a small package with single-maintainer and community support risk, and release notes are sparse. Check commit cadence, open issues, license, and recent releases before committing. Keep an internal fallback path such as direct query export or Laravel Excel if the package stalls or breaks on upgrade. Pin dependencies and validate upgrades in a sandbox.
- What are alternatives to voyager-excel for exporting Voyager data?
- If the application already uses Voyager, evaluate the package against Laravel Excel, PhpSpreadsheet, or a direct query export tailored to your BREADs. If the application does not use Voyager, this package is not applicable and a native Laravel Excel or PhpSpreadsheet approach is preferable. Compare custom format needs, permission handling, and large-export behavior before choosing. Keep the simplest fallback that your team can own.
- Does voyager-excel handle dates, relationships, and null values correctly in exports?
- The assessment recommends validating dates, relations, nulls, and permissions after defining a custom format. The provided context does not guarantee how these values are formatted or resolved for each BREAD. Test representative records, including empty relationships and null fields, before broad rollout. Document expected output so regressions are caught in future upgrades.
- How should I test and upgrade voyager-excel safely in production?
- Use a sandbox install first, validate default exports, then define one custom format for a low-risk BREAD. Validate dates, relations, nulls, permissions, and load-test representative data volumes before expanding. Pin package, Laravel, Voyager, PHP, and spreadsheet dependencies, and review upgrade notes even though v2.2.0 indicates no breaking changes. Keep logging, user-facing errors, and a fallback export path in place.