@burglekitt/gmt-oxlint

Shared Oxlint JS plugin for @burglekitt/gmt projects.

It enforces the same Date bans used by @burglekitt/gmt-eslint and @burglekitt/gmt-biome.

Installation

npm

npm install --save-dev @burglekitt/gmt-oxlint oxlint

yarn

yarn add --dev @burglekitt/gmt-oxlint oxlint

pnpm

pnpm add --save-dev @burglekitt/gmt-oxlint oxlint

bun

bun add --save-dev @burglekitt/gmt-oxlint oxlint

Usage

Quick start (recommended for best DX)

In oxlint.config.ts:

import { defineConfig } from "oxlint";
import { recommendedConfig } from "@burglekitt/gmt-oxlint";

export default defineConfig(recommendedConfig);

If you prefer a custom alias for shorter rule names:

import { defineConfig } from "oxlint";
import { recommendedRules } from "@burglekitt/gmt-oxlint";

export default defineConfig({
  jsPlugins: [{ name: "gmt", specifier: "@burglekitt/gmt-oxlint" }],
  rules: {
    // Copy rules under your alias if you want "gmt/..." rule IDs.
    "gmt/no-date-global": "error",
    "gmt/no-new-date": "error",
    "gmt/no-date-now": "error",
    "gmt/no-date-parse": "error",
    "gmt/no-date-utc": "error",
    "gmt/no-date-getTimezoneOffset": "error",
  },
});

JSON config quick start

In your .oxlintrc.json:

{
  "$schema": "./node_modules/oxlint/configuration_schema.json",
  "jsPlugins": ["@burglekitt/gmt-oxlint"],
  "extends": ["./node_modules/@burglekitt/gmt-oxlint/config/recommended.json"]
}

Oxlint currently resolves extends as file paths. Named shared config specifiers such as @burglekitt/gmt-oxlint/recommended are not currently supported.

Manual configuration

Or explicitly configure each rule. You can use either a string or an array form:

{
  "$schema": "./node_modules/oxlint/configuration_schema.json",
  "jsPlugins": ["@burglekitt/gmt-oxlint"],
  "rules": {
    "@burglekitt/gmt-oxlint/no-date-global": "error",
    "@burglekitt/gmt-oxlint/no-new-date": "error",
    "@burglekitt/gmt-oxlint/no-date-now": "error",
    "@burglekitt/gmt-oxlint/no-date-parse": "error",
    "@burglekitt/gmt-oxlint/no-date-utc": "error",
    "@burglekitt/gmt-oxlint/no-date-getTimezoneOffset": "error"
  }
}

Array form also supported:

{
  "$schema": "./node_modules/oxlint/configuration_schema.json",
  "jsPlugins": ["@burglekitt/gmt-oxlint"],
  "rules": {
    "@burglekitt/gmt-oxlint/no-date-global": ["error"],
    "@burglekitt/gmt-oxlint/no-new-date": ["error"],
    "@burglekitt/gmt-oxlint/no-date-now": ["error"],
    "@burglekitt/gmt-oxlint/no-date-parse": ["error"],
    "@burglekitt/gmt-oxlint/no-date-utc": ["error"],
    "@burglekitt/gmt-oxlint/no-date-getTimezoneOffset": ["error"]
  }
}

Banned patterns

| Pattern | Rule | Suggestion | | -------------------------- | --------------------------- | --------------------------------------------------------------------------------------------------------------------- | | Date global reference | no-date-global | Use getNow(), getUnixNow('milliseconds' or 'seconds'), getUtcNow(), or getZonedNow(timezone) | | new Date(...) | no-new-date | Use getUtcNow(), getNow(), or getZonedNow(timezone) | | Date.now() | no-date-now | Use getUnixNow('milliseconds' or 'seconds') or getNow() | | Date.parse(...) | no-date-parse | Use convertZonedToUnix(value) | | Date.UTC(...) | no-date-utc | Use convertUtcDateTimeToUnix('YYYY-MM-DDTHH:mm:ss', 'milliseconds' or 'seconds') | | date.getTimezoneOffset() | no-date-getTimezoneOffset | Use getZonedNow(timezone), other gmt zoned helpers such as convertZonedToUnix(value), or Temporal.ZonedDateTime |

Why Temporal?

Temporal solves fundamental issues with JavaScript's Date object:

• Immutability: no accidental mutations
• Timezone awareness: explicit, unambiguous timezone handling
• No DST bugs: proper daylight saving time logic
• Precision: nanosecond precision where needed

All banned Date APIs have Temporal equivalents that are safer, clearer, and more correct.

Notes

• Oxlint JS plugins are currently in alpha.
• This package is authored in TypeScript and bundled with tsup for publishing.