Weave Code
Channel Bundle Laravel Package
integrated/channel-bundle
integrated/channel-bundle is a Laravel/PHP package that bundles channel integrations into one consistent package, making it easier to configure, register, and use multiple messaging channels with minimal setup and less boilerplate.
Provides the possibility to use and configure connectors on Integrated installation, which get or distribute content
Frequently asked questions about Channel Bundle
- Can I install integrated/channel-bundle in a Laravel application with Composer?
- Not as a drop-in dependency. Composer may resolve the package, but it ships a Symfony bundle class rather than a Laravel service provider, so there is no auto-discovery and nothing in Laravel will load it. Treat it as a reference implementation to read and port, or run it inside a minimal Symfony app and call it over HTTP or a queue. Any estimate that assumes an in-process Laravel install should be rejected at review.
- What does integrated/channel-bundle actually do?
- It provides a channel registry for Symfony applications: you define channels by name, map them to services or handlers through configuration, and resolve them through a consistent API. Wiring is handled with compiler passes and service tags, so channel-aware services stay decoupled from how channels are declared. It is a lightweight integration layer, not a full messaging or syndication product.
- How do I add a custom connector or channel to the bundle?
- The model is a registry plus an extension contract: you declare a channel in configuration and register the service that implements it via a service tag. The exact interface you must implement depends on what the bundle publishes, so confirm whether extension happens through config, an interface, or both before planning work. Once you know the contract, adding a channel is usually a config entry plus a tagged service.
- Which Laravel and PHP versions does this package support?
- It is not a Laravel package, so Laravel version support is not defined by the bundle at all; what matters is the symfony/* major constraints it declares and whether it hard-requires symfony/framework-bundle. Those constraints are what will conflict with a Laravel 10 or 11 dependency graph. On PHP, read the composer.json require block directly, since anything below 8.1 is a non-starter for a modern Laravel target.
- Is integrated/channel-bundle actively maintained and safe to depend on?
- The project shows zero stars, zero dependents, and no visible release cadence or public issue history, so there is no independent validation of it. Connector layers rot fastest because external APIs, auth schemes, and rate limits change constantly, and an unmaintained one becomes a liability exactly where it matters. Review the last twelve months of commit history before considering any dependency on it.
- How would I reimplement this channel registry natively in Laravel?
- The shape maps cleanly onto Laravel primitives: a Connector contract for each integration, config files for channel definitions, queued jobs for pulls and pushes, and a small registry or manager class resolved from the container. Most teams can build that in roughly a week, with no extra dependency and full control over retries, idempotency, and logging. This read-only reference approach is the cheapest and most maintainable option.
- What security risks come with a connector bundle like this?
- Connectors imply stored third-party credentials and outbound HTTP calls, so secret handling, rotation, and outbound allow-listing all matter. There is no visible evidence in the bundle of SSRF protections, signature verification, or a documented credential strategy, so you must add those yourself. If you run it as a separate service, keep the credentials out of the Laravel app and scope that service's egress.
- Does this bundle work with Laravel's config, service provider, and package discovery?
- No. Symfony bundles load through kernel bundle registration and extension classes, which Laravel does not read, so package discovery will not register anything. Configuration arrives as Symfony bundle configuration rather than Laravel config files, and there is no service provider or facade to publish. You would have to write all the Laravel-side glue yourself, at which point porting the logic is usually simpler.
- What is the execution model for channels, cron, queue, or synchronous?
- The bundle describes routing channels to services or handlers, which suggests synchronous dispatch, but nothing documented defines scheduling, retries, or a queue or messenger transport. Before adopting it, confirm how work is triggered and whether ingest is idempotent and push is reconciled. Those answers determine whether the design survives production traffic.
- When should I run the bundle as an isolated service instead of porting it?
- Choose the isolated-service route only if the connector catalog is large and genuinely hard to reimplement, because you take on a new deployable, a new runtime, and a network hop. Otherwise port the connector concept into a Laravel package, which the MIT license permits, accepting that you then own code from a project with no upstream cadence. As a first step, mining the interface and config schema for a native build is the default recommendation.
Weaver
How can I help you explore Laravel packages today?