Weave Code
Laravel Calendar Events Laravel Package
infyomlabs/laravel-calendar-events
Laravel Calendar Events is a ready-to-use package for adding calendar event management to Laravel apps. It provides models, migrations, controllers, routes, and views for creating, editing, and displaying events in a calendar interface.
Recurring Calendar Events for Laravel.
Frequently asked questions about Laravel Calendar Events
- How do I install infyomlabs/laravel-calendar-events in a Laravel app?
- Install it with Composer using composer require infyomlabs/laravel-calendar-events. The package ships an auto-discovered service provider, so no manual registration is needed in a standard Laravel application. Publish the config and migrations, then run php artisan migrate to create the events table. From there you can create, update, and delete events through the package's fluent API or its Eloquent model.
- Does laravel-calendar-events support Laravel 10 and PHP 8.1?
- The v1.2.0 release is described as a Laravel 10 compatibility update, and the evaluation targets Laravel 10 with PHP 8.1 or newer. However, the release notes do not state whether the illuminate/* and PHP constraints were widened to include 8/9/10 or narrowed to 10 only, which changes whether it is safe for older apps. Read the composer.json diff on the v1.2.0 tag before upgrading, and run your test suite in a scratch install first.
- Can I use laravel-calendar-events with FullCalendar?
- Yes, that is the intended pattern, but the package is a persistence and domain helper rather than a front-end calendar. You store and query events with the package, then expose them as JSON from a controller or API resource for FullCalendar or a custom UI to render. You still own the presentation layer, routes, and any view code you need.
- Does this package support recurring events and RRULE?
- The package overview advertises support for recurring events and custom metadata, so simple repeat definitions may be stored. The technical evaluation stresses that it is not a scheduling or recurrence engine, and there is no evidence of RRULE support, availability calculation, or timezone/DST handling for complex series. If your product depends on true recurrence rules, validate this in a spike or plan to implement recurrence yourself.
- How do I query events by date range for a calendar view?
- The package provides date-range querying specifically so you can fetch only the events visible in the current calendar window rather than loading the whole table. Typical usage is a start and end boundary passed to the query builder, which then returns matching events for that month, week, or day. This keeps calendar rendering fast as the events table grows.
- How do I attach calendar events to my own models, like a User or Project?
- The event model is Eloquent-backed and designed to attach calendar events to arbitrary application models, typically through a polymorphic relation. You add the relation or trait to the models that own events, then create events against that owner via the package API. Because it composes beside your existing domain model rather than replacing it, it slots into an app that already has its own entities and business logic.
- Is laravel-calendar-events a full scheduling or booking system?
- No. It is a lightweight package for storing and retrieving calendar events with an Eloquent model and migrations. It does not provide availability logic, conflict detection, notifications, payments, or a ready-made calendar interface. It fits simple event storage such as bookings, reminders, internal calendars, or timestamped entries where your application handles the surrounding workflow.
- Is the package well tested and safe to use in production?
- The technical evaluation of v1.2.0 found a single-commit compatibility bump from a first-time contributor with no accompanying tests, changelog detail, or evidence of a CI matrix against Laravel 10. That does not make it unusable, but compatibility is asserted rather than demonstrated. Write your own feature tests covering the event model, date-range queries, and timezone behaviour before relying on it in production, and review mass-assignment and output escaping for event fields.
- Is infyomlabs/laravel-calendar-events actively maintained?
- It is maintained but thinly staffed, with release cadence driven by external pull requests rather than a roadmap. The package took well over a year to reach Laravel 10 support, which suggests future framework upgrades could gate your own upgrade path. Check the open issue count, median response time, and last non-bot commit before committing to it long term.
- What are the alternatives to laravel-calendar-events?
- If you only need event persistence with date-range queries, a simple events table with an Eloquent model and a polymorphic owner relation is often the smallest dependency you can add. If you need real recurrence, timezone handling, or two-way sync, look at dedicated calendar or scheduling packages, or build recurrence on top of a library that implements RRULE. Compare each option against your Laravel 10 and PHP 8.1 constraints and check that its version constraints are not narrowed to a single framework release.
Weaver
How can I help you explore Laravel packages today?