- Can I use mybuilder/cronos-bundle in a Laravel application?
- No. It is a Symfony bundle that registers Cronos cron-expression services for Symfony dependency injection and autowiring, and Laravel has no bundle-loading mechanism. For Laravel, depend on dragonmantank/cron-expression or the Cronos parser directly and bind a small CronExpression factory in a service provider. Laravel's scheduler already handles cron-based scheduling natively.
- How do I install mybuilder/cronos-bundle in Symfony?
- Install it with Composer using composer require mybuilder/cronos-bundle, then enable the bundle in your Symfony application's bundle registration. Once enabled, autowiring exposes the Cronos parser services so you can inject CronExpression where needed. Check the latest release date and compatibility with your Symfony and PHP versions before adopting it.
- Does mybuilder/cronos-bundle support Laravel 10 or Laravel 11?
- No. The package has no Laravel service provider, no package auto-discovery, and no Laravel-specific integration. It is built for Symfony bundle registration and Symfony command annotations. In Laravel, only the underlying cron parser is relevant, not this bundle.
- What is the difference between mybuilder/cronos-bundle and dragonmantank/cron-expression?
- mybuilder/cronos-bundle is a Symfony integration wrapper around Cronos, which is a downstream fork of the cron-expression lineage. dragonmantank/cron-expression is the widely used upstream parser and is the safer framework-agnostic choice. The bundle only adds value if you are on Symfony and want autowired Cronos services plus @cron annotations in Symfony commands.
- How do I validate a cron expression in Laravel without this bundle?
- Use dragonmantank/cron-expression directly in a small validation rule or service class. You can bind a CronExpression factory as a singleton in a Laravel service provider and call it from your validator. Do not install the Symfony bundle just to validate user-supplied cron strings.
- Does mybuilder/cronos-bundle work with PHP 8.3 or PHP 8.4?
- The last release was 2023-01-06, so there is no evidence of PHP 8.3 or PHP 8.4 deprecation fixes in the package. Cron syntax itself is stable, but runtime and framework compatibility must be verified against your version matrix. If you need current PHP support, evaluate the maintained upstream parser instead.
- Is mybuilder/cronos-bundle still maintained?
- The latest release is dated 2023-01-06, and the repository has a low public profile. A quiet release cadence is not automatically fatal for a stable cron grammar, but it makes security triage and framework compatibility hard to plan against. Review recent commits, issue activity, and fork divergence before relying on it in production.
- How does Cronos handle DST transitions and timezones in cron schedules?
- Those are parser-behavior questions, and DST skipped or duplicated hours, timezone-explicit evaluation, 5-field versus 6-field expressions, and @reboot or @yearly macros are classic production edge cases. A low-traffic fork is the least likely place to find well-tested coverage for every case. Add tests for your production timezone and DST requirements, and verify next-run calculations explicitly.
- Can I use @cron annotations in Laravel commands with this package?
- No. The @cron annotation handling is part of the Symfony bundle integration for Symfony commands, not a general Laravel feature. Laravel commands and the Laravel scheduler do not scan Symfony bundle annotations. For Laravel, use schedule methods or cron strings directly, or build your own annotation layer if you truly need one.
- What is a lightweight alternative to mybuilder/cronos-bundle for cron parsing in Laravel?
- Use dragonmantank/cron-expression directly and bind a CronExpression factory in a Laravel service provider, or rely on Laravel scheduler's built-in cron methods. If you need next or previous run-time calculations for display or validation, wrap the parser in a small application service. That keeps the dependency surface proportionate and avoids a Symfony-only integration.