Skip to content

Changelog: gmt-oxlint 1.2

  • The core functions, which every industry uses.

Release notes of @northguild/gmt-oxlint 1.2.0 to 1.2.2, newest first, built from packages/gmt-oxlint/CHANGELOG.md. Back to Changelog: gmt-oxlint.

Released 2026-11-03

  • b1cf491: Each package’s npm description and keywords now say what it does. @northguild/gmt names time zones, DST, business days and ISO 8601. Each lint package says it bans the Date object and points to the @northguild/gmt replacement.

    The getTimezoneOffset() lint message in all three lint packages now names getTimeZoneOffset(timeZone, instant) from @northguild/gmt, instead of “zoned methods”.

    The no-date-library-imports message in all three lint packages now names the banned library and links its migration guide on northguild.dev, which maps that library’s calls to their @northguild/gmt replacements. Moment.js, Day.js, Luxon and date-fns each get their own guide; spacetime links the list of guides.

    All three lint packages now also ban @date-fns/tz, the time zone package for date-fns v4. The Biome plugin now bans the same packages as the other two, and no longer flags names outside that list such as moment-tz or luxon-timezone.

Released 2026-09-23

  • 727a3f4: Point the Date.now() and Date.UTC() diagnostics at @northguild/gmt calls that exist (Story CORE-8).

    The Date.UTC() message and README row recommended convertUtcDateTimeToUnix, which @northguild/gmt has never exported. They now name convertUtcToUnix, with the Z the UTC string needs. The Date.now() and Date messages recommended getUnixNow('milliseconds' | 'seconds'), a positional form that @northguild/gmt 1.16.0 replaces with an options object.

    DiagnosticBeforeAfter
    Date.UTC(...)convertUtcDateTimeToUnix('YYYY-MM-DDTHH:mm:ss', 'milliseconds' | 'seconds')convertUtcToUnix('YYYY-MM-DDTHH:mm:ssZ', { epochUnit: 'milliseconds' | 'seconds' })
    Date.now() and the Date globalgetUnixNow('milliseconds' | 'seconds')getUnixNow({ epochUnit: 'milliseconds' | 'seconds' })

    The rules match the same code as before. Only the suggestion text changed, in @northguild/gmt-oxlint, @northguild/gmt-eslint and @northguild/gmt-biome alike.

Released 2026-09-08

  • 4b5d68b: Ban imports of date libraries that wrap or pass native Date objects: moment, moment-timezone, dayjs, luxon, date-fns, date-fns-tz, and spacetime. Reaching for one of these reintroduces exactly the ambient-timezone and DST bugs GMT exists to prevent, so all three linter packages now flag it at the import site rather than waiting for the Date misuse downstream.

    Every specifier form is covered — default, named, namespace, side-effect, type-only, subpaths such as date-fns/format, require(), dynamic import(), and export … from. Relative paths that merely contain a banned name (./my-moment-helper) are not flagged.

    @js-joda/core is deliberately not banned. Its internal representation is its own value types and it touches Date only at the boundary — reading the clock, host zone lookup, and toDate() interop — so it does not carry the problems this ban targets.

    New in each package: no-date-library-imports.grit for Biome (also folded into all.grit), no-restricted-imports plus two no-restricted-syntax selectors for ESLint, and a no-date-library-imports rule for Oxlint, added to its recommended config.

Last updated:

© 2026 NorthGuild · Licences

Code examples: MIT-0. Packages: MIT. Third-party data and components: their own licences, credited where they appear. Everything else: © 2026 NorthGuild, all rights reserved.