Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Event Like Laravel Package

bnnvara/event-like

A Laravel package from BNNVARA that adds like functionality to events, providing traits, migrations, and Eloquent relationships so users can like or unlike events with simple methods for toggling and counting likes.

View on GitHub
Deep Wiki
Context7

Symfony bundle with like events

Frequently asked questions about Event Like
Can I install bnnvara/event-like in a Laravel application?
Not as a drop-in Laravel package. The technical assessment identifies bnnvara/event-like as a Symfony bundle, and Laravel does not load Symfony bundle registration, Extension classes, or CompilerPass wiring. You can only reuse framework-agnostic domain classes or port the bundle wiring into a Laravel service provider.
Is bnnvara/event-like a Laravel package or a Symfony bundle?
The provided context is contradictory: the blurb calls it a Laravel package, while the technical evaluation says it is a Symfony bundle. Treat the Symfony bundle finding as the critical constraint because Laravel has no equivalent bundle lifecycle. Audit the source before assuming any Laravel compatibility.
How do I install bnnvara/event-like with Composer?
A normal Packagist install is not confirmed because the repository is Bitbucket-hosted and described as a Symfony bundle. You would need Composer repository configuration and Bitbucket access to require it. Even after installation, a Laravel app will not auto-register Symfony bundle services.
Does bnnvara/event-like support Laravel 10 or Laravel 11?
There is no verified Laravel 10 or Laravel 11 support in the provided context. The package is presented as a Symfony bundle, not a Laravel service provider package. Any Laravel version support would depend on porting the code and checking its PHP and Symfony constraints.
What does event-like actually do: like events, persistence, or both?
The name and description are ambiguous. The blurb says it provides traits, migrations, and Eloquent relationships for liking and unliking events with toggle and count methods. The technical assessment warns it may instead emit domain events, persist likes, or do both, so a source audit is required.
Does bnnvara/event-like use Eloquent or Doctrine?
The blurb mentions Eloquent relationships and migrations, but the technical assessment warns that Symfony bundles often depend on Doctrine. The persistence layer is not verified from the provided context. If Doctrine entities or repositories are present, replace them with Eloquent models and first-party migrations rather than bridging ORMs.
How do I configure bnnvara/event-like in a Laravel service provider?
There is no documented Laravel configuration because the package is described as a Symfony bundle. If you proceed, extract the domain code and expose services through an Illuminate Support ServiceProvider with explicit bindings and config merging. Do not attempt to run Symfony dependency injection compilation inside Laravel.
Can I use its Symfony event classes with Laravel's event dispatcher?
Possibly, but only if the event classes are framework-agnostic and compatible with the contracts Laravel dispatches. Laravel implements its own dispatcher contract and recent PSR-14 support, but Symfony bundle listener tagging and DI auto-configuration will not transfer. You would need to re-register listeners and subscribers in Laravel explicitly.
How do I test like and unlike idempotency in bnnvara/event-like?
The provided context gives no evidence of an existing test suite, so you should write tests around the ported behavior. Cover duplicate likes, unlike of a non-liked event, count accuracy, and concurrent toggle attempts. Use database transactions or RefreshDatabase in Laravel and assert the pivot constraints enforce idempotency.
Is bnnvara/event-like maintained, licensed, and safe for production?
The technical assessment flags high supply-chain risk: zero stars, zero dependents, Bitbucket hosting, and no visible CI, tests, release cadence, or license verification. It also notes an effective bus factor of one with no downstream validation. For production, prefer an in-house polymorphic likes pivot with Eloquent relationships, toggle methods, and Laravel events, or a maintained Laravel favorites package.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
htinlynn/genius-helper
maco-studios/hephaestus
elmogy/larafast
xeviant/laravel-paystack
gorilladash/laravel-website-sdk
martialbe/flysystem-oss
chondal/3312client
jeroen-g/flickr
opscale-co/nova-genbi
itsjustvita/laravel-retention
tequilarapido/trackit
gregsphotography/site-builder-filament
cabaoctavio/laravel-query-log
gregsphotography/site-builder-components
io-digital/clickatell
snowsoft/laravel-admin
oxygen/auth
relicsoftware/barakah-payment-gateway
tobya/work-with-composer
equipc/laravel-email-validator