Weave Code
Lenats Laravel Package
lebrains/lenats
Lenats is a Laravel integration for NATS, the lightweight, high-performance messaging system. It offers a simple, Laravel-style API for publishing and subscribing to subjects, so you can add event-driven messaging to your applications with minimal setup.
DEPRECATED: The LeNats is a Symfony bundle. it's implements event-based architecture with nats streaming on php
Frequently asked questions about Lenats
- Is lebrains/lenats a Laravel package?
- No. The project describes itself as a Symfony bundle, not a Laravel package, and it assumes Symfony's service container, bundle registration, event dispatcher, and configuration model. It is not built around Laravel service providers, facades, or package discovery conventions. Treat it as a reference for event-based messaging concepts rather than a drop-in Laravel dependency.
- Can I install lebrains/lenats in a Laravel app?
- You can add it with Composer only as a Symfony bundle, not as a Laravel-native package. Using it in Laravel would require Symfony components, custom bootstrapping, a compatibility bridge, or a fork. The technical assessment rates integration feasibility low and recommends a Laravel-compatible NATS client or an internal adapter instead.
- Why is LeNats deprecated?
- The repository is explicitly marked DEPRECATED and archived. The assessment also notes that its NATS Streaming target is deprecated in favor of NATS JetStream, which compounds the maintenance and architecture risk. The provided context does not give an official deprecation rationale beyond those signals.
- Does LeNats support NATS JetStream?
- The provided evaluation says LeNats targets NATS Streaming, not JetStream. NATS Streaming is deprecated, so long-term compatibility with the broader NATS ecosystem is already degraded. New Laravel work should plan around a maintained JetStream-capable client instead.
- Which Laravel and PHP versions does LeNats support?
- There is no reliable Laravel or PHP version support listed in the provided context. Because it is an archived Symfony bundle, compatibility with current Laravel and PHP releases is not guaranteed. Treat any version claims as unverified and expect to own upgrades if you fork it.
- Is LeNats safe for production Laravel applications?
- The assessment rates technical risk high for a Laravel production roadmap. Risks include archived code, no security patch path, GPL-3.0 licensing implications, a deprecated NATS Streaming dependency, and Symfony/Laravel impedance mismatch. It is not recommended for new Laravel production adoption.
- What license does LeNats use?
- The technical assessment identifies GPL-3.0. That requires legal review before embedding in a commercial or proprietary Laravel product because GPL obligations can affect distribution and derivative works. Confirm the licensing implications with counsel before adopting or forking the package.
- What are alternatives to LeNats for NATS messaging in Laravel?
- Use a maintained NATS or JetStream PHP client and wrap it behind an internal adapter interface. That keeps Laravel application code decoupled from the transport and makes future client changes cheaper. Avoid adopting an archived Symfony bundle just to add NATS connectivity to Laravel.
- How do I test LeNats in a Laravel application?
- The provided context does not document Laravel testing helpers for LeNats. Testing would likely require Symfony bootstrapping and a live or mocked NATS Streaming setup, which is heavy for a Laravel application. A safer approach is to put the transport behind an adapter interface and test against a fake implementation plus contract tests.
- How do I migrate from LeNats to a supported NATS client?
- First inventory existing LeNats usage and message contracts, then isolate legacy code behind an anti-corruption layer. Run a spike with a maintained NATS or JetStream client in Laravel, build an internal adapter, and migrate producers and consumers with dual-publish or replay where needed. Preserve event contracts during migration and decommission LeNats and NATS Streaming only after the replacement path is proven.
Weaver
How can I help you explore Laravel packages today?