- Is mopa/feed-bundle compatible with Laravel?
- No. It is a Symfony 2-era bundle built around Symfony's Bundle, DependencyInjection, and EventDispatcher model. It has no Laravel service provider, package discovery, facade, or publishable config, so it does not map onto Laravel without a custom bridge or fork.
- How do I install mopa/feed-bundle in a Laravel application?
- You should not install it directly in a modern Laravel app. Composer constraints are expected to conflict with Symfony 2.x pins and abandoned zendframework/zend-feed dependencies, forcing --ignore-platform-reqs or alias-based substitution. That shifts risk onto your application and still leaves you without Laravel-native integration.
- Does mopa/feed-bundle support Laravel 10 or Laravel 11?
- No. There is no evidence of Laravel 10 or Laravel 11 support; the package predates modern Laravel and is tied to Symfony 2-era components. The PHP version floor and pre-PHP 8 idioms make it unsuitable for current Laravel version matrices. Treat any claimed Laravel support as unverified.
- What does mopa/feed-bundle actually do?
- It renders RSS and Atom feeds from content collections using Symfony bundle conventions and controller annotations. The repository is a feed rendering bundle; despite the overview text mentioning "Websocket and Feedfunctionality," there is no websocket transport, socket server, or pub/sub code in the package. Treat the description as unreliable.
- Does mopa/feed-bundle provide websockets or realtime push?
- No. The stated description mentions websocket functionality, but the repository contains feed rendering code only. For realtime push in Laravel, evaluate laravel/reverb, soketi, or a managed Pusher-compatible service as a separate workstream.
- Can I use mopa/feed-bundle to generate RSS and Atom feeds in Laravel?
- Only by forking or bridging it, not as a normal dependency. It would run a second DI container and HTTP kernel alongside Laravel for a feature that produces XML. The practical option is to use a Laravel-native feed package such as spatie/laravel-feed, validated against your Laravel version matrix.
- What are the best alternatives to mopa/feed-bundle for Laravel?
- For feed output, spatie/laravel-feed is the obvious Laravel-native candidate to validate at spike time. For websocket functionality, which mopa/feed-bundle does not actually provide, use laravel/reverb, soketi, or a managed Pusher-compatible service. If you must preserve exact behavior, port the feed-generation semantics into an internal contract instead of depending on the bundle.
- Is mopa/feed-bundle maintained?
- No. Last activity is Symfony 2 era, with a single maintainer and zero stars or dependents. There is no downstream usage to lean on for compatibility evidence and no active issue history for known failure modes. Adopting it would make you the de facto maintainer of a fork.
- What dependencies does mopa/feed-bundle require?
- Expect Symfony 2.x component pins, doctrine/annotations, and a transitive dependency on the abandoned zendframework/zend-feed line. Any fork should swap zendframework/* for laminas/laminas-feed and update pre-PHP 8 idioms. These constraints are a primary reason Composer will not resolve in a modern Laravel application.
- How should I test or audit a fork of mopa/feed-bundle?
- Treat it as a reference implementation and extract feed-generation semantics behind an internal contract, for example FeedGeneratorContract::render(FeedDefinition): string. Implement that contract natively with Laravel XML or laminas-feed, then test output for RSS and Atom validity, escaping, and byte-for-byte behavior against any existing consumer. Also review XML generation and escaping because the code predates modern PHP and has no advisory or CVE monitoring.