- Is grofgraf/laravel-pdf-merger compatible with Laravel 10 and Laravel 11?
- The package's last release was March 2019, in the Laravel 5.8 and PHP 7.x era. There is no evidence of Laravel 9, 10, or 11 support, and its Composer constraints may block installation on modern Laravel. Test composer require in a throwaway branch and review its composer.json constraints before adopting it.
- How do I install laravel-pdf-merger with Composer?
- Install it with composer require grofgraf/laravel-pdf-merger and let Laravel package discovery register the service provider if supported. If discovery is not available, register the provider manually in config/app.php. The main risk is dependency resolution against your PHP and Laravel versions, so run the install in a disposable environment first.
- What does laravel-pdf-merger actually do?
- It merges multiple PDF files into a single PDF while preserving input order. It is a bounded utility, not a document management system, and should sit behind an application service or queue job. It does not add infrastructure; it runs in-process in PHP-FPM or a queue worker.
- Does laravel-pdf-merger support uploaded PDFs and Laravel filesystem storage?
- The package is described as supporting stored or uploaded PDFs and integrating with Laravel's filesystem. That means you can pass files from Storage or an UploadedFile after moving it to a temporary path, depending on the wrapper's API. Confirm the accepted input types such as paths, streams, UploadedFile, or base64 in the repository before wiring it in.
- Is laravel-pdf-merger still maintained?
- The last release date is 2019-03-28, with a single maintainer and no visible CI or test coverage. That is roughly six years without a release, so treat it as stale. For production, either fork it, pin it, or own the thin wrapper yourself.
- What library does laravel-pdf-merger use to merge PDFs?
- The package is a thin Laravel wrapper around a third-party PDF merge library, likely iio/libmergepdf or similar. The underlying library carries the real merge logic and the real CVE exposure. Check its version, license, and composer audit results before relying on it.
- Is laravel-pdf-merger safe for large PDF files and memory limits?
- A PDF merger can buffer whole documents in PHP memory, so large inputs may hit memory_limit. Test with files above 100 MB and monitor whether it streams to temp files or holds everything in memory. Run merges in a queue worker with an explicit memory limit rather than in a web request.
- Does laravel-pdf-merger handle encrypted or password-protected PDFs?
- Encrypted, password-protected, and malformed PDFs are common runtime failure modes for PDF merge libraries. The package documentation does not establish support for encrypted inputs, so verify empirically with representative files. If encrypted PDFs are a requirement, test the underlying library directly before committing.
- Should I use laravel-pdf-merger or the underlying PDF library directly?
- If the underlying library is usable without the package, the package's value is mostly container wiring and a facade. That is roughly 50 lines of adapter code you could own. Going one level down avoids an abandoned layer but means you take on dependency updates and CVE tracking yourself.
- Is laravel-pdf-merger MIT licensed for commercial projects?
- The package is MIT licensed, which is compatible with commercial and self-hosted distribution. That is its cleanest signal. Licensing does not resolve the maintenance and dependency risks, so keep those separate in your evaluation.