- How do I install petecoop/odt in a Laravel application?
- Install it with composer require petecoop/odt. Laravel package auto-discovery registers the service provider, so you normally do not need a manual provider entry. If the package ships a config file, publish it with php artisan vendor:publish and commit the result. Confirm the release you install matches your Laravel version before running composer update in production.
- Which Laravel and PHP versions does petecoop/odt support?
- Release 1.1.0 added Laravel 13 support, and the package is described as tracking Laravel's release cadence. Before relying on a specific matrix, read the composer.json illuminate/* constraints: they may allow Laravel 11, 12, and 13, or they may be pinned to 13 only. The PHP floor follows from those framework constraints, so check it in CI base images too. The release notes alone do not state the exact supported versions.
- Does petecoop/odt 1.1.0 break Laravel 11 or 12 applications?
- It should not if the Laravel 13 work widened the constraints, for example ^11.0|^12.0|^13.0. It would break them if the constraints were replaced with ^13.0 only, because that is a semver violation inside a minor release. Version 1.1.0 is a minor bump from 1.0.x, so backwards compatibility is promised, but verify the composer.json diff before upgrading apps on Laravel 11 or 12. Pin your current version until you have confirmed the constraint matrix.
- What changed in petecoop/odt version 1.1.0?
- Version 1.1.0 is a maintenance release: Laravel 13 support, an internal refactor, a Testbench upgrade, and lint and formatting cleanup. Nothing in the notes indicates a new public API, integration pattern, or change in how the package is composed into an application. The refactor is the item to review because it can change behaviour without changing the version contract. The Testbench upgrade is dev-only and affects the package's own test suite.
- How do I generate an ODT file from a template with petecoop/odt?
- petecoop/odt generates OpenDocument Text (.odt) files, which are editable word-processing documents suitable for download or export. You provide templates and structured data, then use the package's API to build the document response. The exact facade, class names, and template syntax are not included in the supplied release notes, so check the repository README for the current usage example. Because ODT is an open standard, generated files open in LibreOffice, OpenOffice, and Word with varying fidelity.
- Do I need to publish the petecoop/odt configuration file?
- It is a conventional Laravel package with a service provider and config publishing. Publish it with php artisan vendor:publish and commit the config so changes are visible in review. If the 1.1.0 refactor renamed or removed config keys, republish and diff config/ rather than overwriting your existing file. That prevents silent behaviour changes after composer update.
- How should I upgrade petecoop/odt to 1.1.0 safely?
- Pin the version you run today, create a branch, bump to 1.1.0, and run your application test suite. Read the composer.json diff and any CHANGELOG first to establish the constraint matrix, then review the refactor diff for public-surface changes. Smoke-test the package's user-facing surfaces: routes, commands, scheduled jobs, config publishing, and any queue workers it registers. No data migrations or schema changes are implied, and the previous version is your rollback target.
- Is petecoop/odt safe and production-ready for a Laravel app?
- Technical risk is assessed as low to moderate. The package is architecturally neutral and the 1.1.0 changes are mostly maintenance, but the internal refactor is the one opaque item that could affect service provider registration order, container binding keys, extension points, config keys, or command signatures. Verify those and confirm orchestra/testbench stayed in require-dev. Do not couple the package bump to a Laravel major upgrade; sequence those as separate changes.
- Does petecoop/odt use Testbench, and does that affect production dependencies?
- Yes, the package uses orchestra/testbench for its own test suite, and 1.1.0 upgraded it. That is a dev dependency and should not enter your production dependency graph. Confirm it stayed in require-dev in the composer.json diff. Coverage parity after the Testbench migration is worth checking if you rely on the package's tests as a quality signal.
- What are the alternatives to petecoop/odt for document generation in Laravel?
- The release notes do not name alternatives, so evaluate based on output format: choose petecoop/odt when you need OpenDocument Text (.odt) with Laravel-native integration. If your consumers expect .docx specifically, a DOCX-focused library may fit better, and for PDF output you should use a PDF renderer instead. Also compare the package's maintenance cadence and bus factor against your support requirements.