- Can I install pk/markdownify-bundle in a Laravel application?
- No. pk/markdownify-bundle is a Symfony2 bundle that registers the Markdownify converter through Symfony's DI extension, Configuration, and service definition; Laravel has no bundle system, service-provider auto-discovery, or Symfony AppKernel registration. Installing it directly will also run into Symfony 2.x and PHP version constraints that conflict with modern Laravel. For Laravel, use a maintained HTML-to-Markdown library and wrap it in a Laravel service provider.
- Does pk/markdownify-bundle support Laravel 10 or Laravel 11?
- No. Laravel 10 and 11 require PHP 8.1+ and modern Symfony components, while this bundle's last release was 2019-05-15 and targets Symfony 2.x with older PHP constraints. Composer resolution will normally fail, and forcing installation with --ignore-platform-reqs is likely to cause missing classes or runtime incompatibilities.
- What is pk/markdownify-bundle used for?
- It provides Symfony integration for the Markdownify and Markdownify_Extra scripts, converting HTML content into Markdown. Its main job is to register the underlying converter as a Symfony service and integrate with Symfony services and Twig. It is not a Laravel package and does not provide Laravel facades, config publishing, or package discovery.
- Is pk/markdownify-bundle actively maintained?
- No. The repository is archived, meaning it is read-only with no issue triage, no maintenance, and no security patches. The last release was 2019-05-15, and the project has very little community validation at 3 stars and 0 dependents. Treat it as abandoned for new development.
- What Laravel alternative should I use for HTML to Markdown conversion?
- league/html-to-markdown is the common Laravel-compatible choice cited for this use case. Bind it behind a small interface in a Laravel service provider so controllers and jobs do not depend directly on the library. Evaluate its current maintenance status and test your real HTML edge cases before adopting it.
- How can I use Markdownify for HTML to Markdown in Laravel if I must?
- Do not install the Symfony bundle. Identify the underlying Markdownify converter library, install that library directly only if it is maintained and compatible with your PHP version, then pin it and run a dependency and CVE review. Wrap the converter in a Laravel service provider and add tests for tables, nested lists, and inline HTML; if it is not maintained, vendor a reviewed fork with a named owner.
- Why does Composer conflict when installing pk/markdownify-bundle with Laravel?
- The bundle targets Symfony 2.x components and older PHP constraints, while modern Laravel applications use Symfony 6 or 7 components and PHP 8.1+. Composer therefore cannot resolve a compatible dependency set. Using --ignore-platform-reqs does not fix the underlying API and runtime differences.
- Is pk/markdownify-bundle compatible with PHP 8?
- It is not designed for PHP 8. The last release in 2019 predates modern PHP 8 support, and the archived repository will not receive PHP 8+ compatibility fixes. Even if the underlying converter class happens to run, you must test it against your PHP version and accept the maintenance risk.
- Can I use the Twig integration from pk/markdownify-bundle in Laravel?
- No. The Twig integration is part of the Symfony bundle wiring and assumes Symfony bundle registration and service conventions. Laravel does not use Symfony bundles, and its Twig or Blade integrations are separate. Use a maintained converter directly and expose it through a Laravel helper, facade, or Blade directive if needed.
- Is pk/markdownify-bundle safe for production Laravel applications?
- It is high risk. The repository is archived with no security patching or support, and its Symfony 2.x dependency chain is end-of-life and may carry known CVEs. The MIT license is permissive, but that does not offset the lack of maintenance. For production Laravel, choose a maintained converter or a reviewed fork with clear ownership and an exit plan.