- How do I install mrshanebarron/calendar in a Laravel app?
- Run composer require mrshanebarron/calendar, publish the config file, set your values, and clear cached config. Because v1.0.1 renamed the config file, install fresh rather than assuming a v1.0.0 layout. Inventory exactly what the package publishes or registers during install so nothing is missed.
- Which Laravel and PHP versions does mrshanebarron/calendar support?
- The provided release information does not list tested Laravel or PHP constraints, so check the package's composer.json and CI status before installing. Compare its required Laravel version against your application's composer.json first, because a mismatch ends the evaluation cheaply. Confirm PHP version alignment in the same pass.
- Why did the mrshanebarron/calendar config file name change in v1.0.1?
- v1.0.1 changed the config filename to correct an inconsistent sb- prefix. That is a compatibility-relevant change shipped in a patch release, so treat the upgrade as an implicit minor or breaking change if you customized config at 1.0.0. The realistic failure is a silent fallback to package defaults rather than a crash.
- How do I migrate from mrshanebarron/calendar v1.0.0 to v1.0.1?
- Capture your customizations from the v1.0.0 config file, re-publish the config under the new v1.0.1 filename, then diff and re-apply. Delete the stale file and run php artisan config:clear, rebuilding config:cache if production caches config. Verify by asserting on resolved values, not by reading the file.
- Does mrshanebarron/calendar add routes, migrations, views, or a facade?
- The release note confirms configuration is a first-class concern but does not state whether the package also ships routes, migrations, views, or a facade. Inventory exactly what gets published or registered after installing in a throwaway branch. That footprint changes the adoption blast radius, so verify it before rolling out.
- How do I build and display a calendar with date-based events?
- The package provides configurable calendar views and helpers for date-based events, scheduling, availability, and date ranges. Start by publishing the config file, setting defaults or overrides, and clearing cached config. Exercise both default and overridden behavior in a scratch app before wiring it into application screens.
- Is mrshanebarron/calendar production ready and well maintained?
- Treat it as an early 1.x package: the public surface is weeks old and the config contract has already moved once. Budget for churn and stage upgrades before production. Check the license, maintainer bus factor, changelog, and config-resolution test coverage directly in the repository, since the provided release notes do not cover them.
- What is the sb- config prefix in mrshanebarron/calendar?
- The config file is namespaced under an sb- prefix, which appears to be the package's vendor or slug prefix. Do not hardcode the config path anywhere in application code, because the prefix and filename have already changed once. Resolve values through Laravel's config system instead.
- How do I test calendar behavior and config overrides in Laravel?
- Assert on resolved config values rather than eyeballing the published file. Run feature tests that exercise the calendar's default behavior and each override, and diff resolved config when upgrading. Use a staging environment for the config migration and clear or rebuild config caches after changes.
- What are alternatives to mrshanebarron/calendar for Laravel calendars?
- Compare other Laravel calendar packages only after confirming this package's Laravel constraint, license, and published footprint. The key differentiators are whether an alternative ships views, routes, or migrations and how stable its config contract is. Because mrshanebarron/calendar is early 1.x, keep the integration behind a thin wrapper so swapping stays cheap.