- Can I install fbeen/pdf-bundle in a Laravel application?
- No. It is a Symfony bundle that extends Symfony's Bundle class and relies on the DI container extension and config-tree compilation pipeline, neither of which exists in Laravel. Laravel ships some Symfony components, but it has no bundle registry, so this package cannot be registered from a service provider as-is. For Laravel you should evaluate a native renderer or wrap the underlying psliwa/php-pdf library directly.
- What does fbeen/pdf-bundle actually do?
- It is a thin Symfony2 integration layer around the PHPPdf library (psliwa/php-pdf) that lets you turn HTML or Twig templates into PDF documents. It mainly provides service wiring, configuration, and a convenience API so Symfony applications get PDF export with minimal setup. The PDF rendering itself is done by the upstream library, not by the bundle.
- Is fbeen/pdf-bundle a Laravel package, and which Laravel versions does it support?
- It supports none. The package is a Symfony bundle targeting Symfony 3.3-era applications, which implies PHP 5.x/7.0 constraints, so it will not even install cleanly on modern PHP 8.x runtimes. There is no Laravel 9, 10, 11, or 12 support and no Laravel service provider is shipped. Treat any claim that it works with Laravel as inaccurate.
- What should Laravel developers use instead of fbeen/pdf-bundle for HTML-to-PDF?
- Pick a renderer based on fidelity and runtime requirements: dompdf or laravel-dompdf for simple HTML, mPDF for Unicode and CJK-heavy documents, Snappy/wkhtmltopdf for legacy layout fidelity, or Browsershot for Chromium-grade CSS support. All of them are plain Composer packages you can bind behind your own PdfRenderer interface and swap later. That gives you a clean upgrade path without inheriting a Symfony-only fork.
- Is fbeen/pdf-bundle maintained and safe to use in production?
- It shows zero stars, zero dependents, and a single maintainer, with no community validation or downstream bug surface. There is no discoverable security disclosure path and no CVE coverage for the fork, so supply-chain review will flag it. Because it is a compatibility fork, upstream fixes are not guaranteed to be tracked, which means you inherit a private maintenance burden from day one.
- Can I use psliwa/php-pdf directly in Laravel without the Symfony bundle?
- Yes. The underlying psliwa/php-pdf library is plain PHP and installs via Composer without any Symfony bundle machinery, so it can be called from a Laravel service or job. Wrap it behind your own small interface so you can replace it later, and verify first that it passes your PHP 8.x compatibility check and your font/script requirements. For most greenfield Laravel projects a Laravel-native renderer is still the better default.
- How do I generate a PDF from a Blade view in Laravel without a Symfony bundle?
- Render the Blade template to an HTML string with view('pdf.invoice', $data)->render(), then hand that HTML to a renderer such as laravel-dompdf, mPDF, or Browsershot and stream or store the output. Keep the render call inside a queued job for large documents so request latency stays predictable. This pattern covers the same HTML-or-Twig-to-PDF use case the bundle advertises, without any Symfony coupling.
- What is the difference between fbeen/pdf-bundle and psliwa/pdf-bundle?
- fbeen/pdf-bundle is a compatibility patch fork of psliwa/pdf-bundle, created so the bundle installs against Symfony 3.3 rather than adding new rendering features. That means its stated value proposition is a Composer constraint fix, not a functional improvement. For a Laravel codebase that value is effectively zero, since the constraint it patches does not apply.
- How do I migrate an existing Symfony 3.3 PDF export to a Laravel application?
- Start with requirements capture: document types, volume, fidelity bar, Unicode or CJK needs, digital signatures, and latency budget. Run a fidelity spike by rendering three representative documents (largest, most complex layout, non-Latin text) through a candidate Laravel renderer and comparing output to the current system. If an existing Symfony service already depends on this fork, treat it only as a stopgap to unblock Composer resolution and schedule an exit.
- Does fbeen/pdf-bundle handle Unicode, CJK text, or digital signatures?
- Those capabilities come from the underlying PHPPdf library rather than the bundle, so the bundle inherits whatever the pinned upstream version supports. Font and script coverage for CJK or Arabic documents is limited and often requires explicit font registration and configuration. Digital signatures and PDF merging are generally not first-class features here, so if you need them, evaluate a renderer that documents them explicitly.