- How do I install ueberdosis/pandoc in a Laravel application?
- Install the package with Composer using composer require ueberdosis/pandoc. In Laravel, follow the package README for service provider registration or package auto-discovery. Make sure the Pandoc binary is installed on the host and available on PATH or through the package configuration.
- Does ueberdosis/pandoc require Pandoc to be installed on the server?
- Yes. ueberdosis/pandoc is a PHP wrapper around Pandoc, so the Pandoc executable must be installed and available to your PHP process. Verify the binary path in local, CI, and production environments, especially if your deployment uses containers or restricted PATH settings. PDF output may also require additional Pandoc PDF engines such as LaTeX depending on your conversion target.
- What document formats can I convert with ueberdosis/pandoc?
- The package wraps Pandoc, so it can convert between formats Pandoc supports, including Markdown, HTML, DOCX, and PDF. The exact input and output combinations depend on the installed Pandoc version and any required external tools. Check your target format against Pandoc's reader and writer support before building production workflows.
- Can I use ueberdosis/pandoc in plain PHP without Laravel?
- The package is described as a fluent PHP and Laravel wrapper, so its core conversion API should be usable from PHP applications. Laravel-specific features such as auto-discovery or configuration publishing may not apply outside Laravel. Review the README for the recommended plain PHP setup and any framework-dependent integrations.
- What does noStandalone() do in ueberdosis/pandoc 0.9.0?
- Version 0.9.0 adds noStandalone() to disable Pandoc's --standalone option. This gives integrators programmatic control over whether standalone mode is available or active for a conversion path. Review the 0.9.0 diff and documentation to confirm whether it applies globally, per command, or only to a specific invocation before relying on it in production.
- Is ueberdosis/pandoc compatible with Laravel 10 and Laravel 11?
- The provided package evaluation does not list exact Laravel and PHP version constraints, so verify composer.json and the README for the supported framework versions. The package targets Laravel applications, but compatibility should be confirmed for your specific Laravel and PHP matrix. Pin to ^0.9 and run your application tests before upgrading across major Laravel versions.
- How should I test document conversions with ueberdosis/pandoc in CI?
- Write integration tests that cover real conversions where possible and mock the process layer only if the package exposes a suitable seam. Include cases for --standalone enabled, disabled through noStandalone(), and omitted so command behavior is deterministic. Validate output content and failure handling, and make sure the CI runner has the required Pandoc binary and PDF tooling.
- What are alternatives to ueberdosis/pandoc for Markdown to PDF conversion in PHP?
- Alternatives include calling the Pandoc binary directly, using league/commonmark with a PDF renderer for simpler HTML-to-PDF flows, or evaluating other PHP Pandoc wrappers. ueberdosis/pandoc is most useful when you want a fluent API and Laravel-friendly integration around Pandoc. Choose based on whether you need broad format support or a narrower Markdown-to-PDF pipeline.
- Is ueberdosis/pandoc production-ready at version 0.9?
- The package is pre-1.0, so minor releases may still carry behavioral nuance even when changes are additive. The 0.9.0 noStandalone() feature is low to moderate risk, but you should pin to ^0.9 and test command behavior before broad rollout. Treat upgrades as controlled changes and document how standalone mode is managed in each environment.
- How do I control Pandoc options such as --standalone with ueberdosis/pandoc?
- Use the package's fluent API and configuration to pass Pandoc options, and use noStandalone() in 0.9.0 when standalone mode must be disabled. Confirm from the documentation where noStandalone() must be called and whether it affects command signatures or runtime command construction. Add tests for standalone enabled, disabled, and omitted cases to avoid local and CI behavior diverging.