🚀 Features
- remove date-fns localization, use Intl api, update date-fns to latest - by @felixmosh 38ce164
- Add Docs & Demo site - by @felixmosh in #1217 (37fbf)
- Update docs with queue adapters - by @felixmosh (d1354)
- Cleanup README.md - by @felixmosh (14ede)
- docs: Update references to include BullMQ Pro and rearrange navigation menu - by @felixmosh (2a361)
- ui: Add German (de-DE) locale - by @MikeGrote in #1215 (c049d)
🐞 Bug Fixes
- Update mock adapter imports - by @felixmosh (c435f)
💣 Breaking Changes
- Remove
date-fnslocale, migrate toIntlAPI
DateFormats now uses Intl.DateTimeFormatOptions
The short, common, and full properties of DateFormats previously accepted
date-fns format strings (e.g. "HH:mm:ss"). They now require
Intl.DateTimeFormatOptions objects.
- short?: string;
- common?: string;
- full?: string;
+ short?: Intl.DateTimeFormatOptions;
+ common?: Intl.DateTimeFormatOptions;
+ full?: Intl.DateTimeFormatOptions;Migration example:
- dateFormats: { short: 'HH:mm:ss' }
+ dateFormats: { short: { hour: 'numeric', minute: 'numeric', second: 'numeric' } }The date-fns locale was resolved internally from the lng setting. The Intl API
now uses the runtime's built-in locale data — no extra locale modules are needed