@ttsc/lint 0.13.1 → 0.14.0-dev.20260528

package/src/structures/rules/ITtscLintJsxA11yRules.ts

@@ -0,0 +1,339 @@
+import type { TtscLintRuleSetting } from "../TtscLintRuleSetting";
+
+/**
+ * JSX accessibility rules from `eslint-plugin-jsx-a11y`, applied to
+ * TSX (and JSX-in-TS) sources.
+ *
+ * Checks the static structure of JSX elements against WAI-ARIA
+ * authoring guidance — interactive controls should be focusable,
+ * labels should reference a control, ARIA properties should match the
+ * element role, and so on. Runtime accessibility issues require live
+ * audits; this family catches the statically-decidable subset.
+ *
+ * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y
+ */
+export interface ITtscLintJsxA11yRules {
+  /**
+   * Require image-like JSX elements (`<img>`, `<input
+   * type="image">`, `<object>`, `<area>`) to expose alt text or an
+   * ARIA label.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/alt-text.md
+   */
+  "jsx-a11y/alt-text"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `<a>` elements whose visible text is one of a small set of
+   * phrases that carry no information out of context. Screen-reader
+   * users navigate by listing links — "click here" / "more" / "read
+   * more" turn that list into noise.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/anchor-ambiguous-text.md
+   */
+  "jsx-a11y/anchor-ambiguous-text"?: TtscLintRuleSetting;
+
+  /**
+   * Reject empty JSX anchors with no accessible content (text,
+   * `aria-label`, or labelled child).
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/anchor-has-content.md
+   */
+  "jsx-a11y/anchor-has-content"?: TtscLintRuleSetting;
+
+  /**
+   * Reject anchors with missing, `#`-only, empty, or `javascript:`
+   * `href` values, all of which break navigation semantics.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/anchor-is-valid.md
+   */
+  "jsx-a11y/anchor-is-valid"?: TtscLintRuleSetting;
+
+  /**
+   * Require `tabIndex` on any element carrying `aria-activedescendant`
+   * unless the tag is already focusable by default (`<input>`, etc.) —
+   * the composite-widget host must keep document focus for the
+   * descendant id to do anything.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/aria-activedescendant-has-tabindex.md
+   */
+  "jsx-a11y/aria-activedescendant-has-tabindex"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `aria-*` JSX attribute names that are not part of the
+   * WAI-ARIA States and Properties spec — catches typos such as
+   * `aria-labeledby` (missing second `l`) that silently disable
+   * assistive-tech support.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/aria-props.md
+   */
+  "jsx-a11y/aria-props"?: TtscLintRuleSetting;
+
+  /**
+   * Validate literal values supplied to ARIA properties against the
+   * type the spec declares for them — e.g. `aria-checked` must be
+   * one of `true`, `false`, `"mixed"`, and `aria-hidden="yes"` is
+   * rejected because the type is boolean.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/aria-proptypes.md
+   */
+  "jsx-a11y/aria-proptypes"?: TtscLintRuleSetting;
+
+  /**
+   * Require `role` values to be a concrete, non-abstract WAI-ARIA role
+   * (`"button"`, `"checkbox"`, ...). Rejects misspellings and abstract
+   * roles like `"range"`; computed values are skipped because the
+   * concrete role cannot be checked statically.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/aria-role.md
+   */
+  "jsx-a11y/aria-role"?: TtscLintRuleSetting;
+
+  /**
+   * Reject ARIA roles and attributes on elements that do not
+   * support them (e.g. `aria-checked` on a `<meta>` tag).
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/aria-unsupported-elements.md
+   */
+  "jsx-a11y/aria-unsupported-elements"?: TtscLintRuleSetting;
+
+  /**
+   * Validate the literal `autocomplete` token against the HTML spec
+   * vocabulary and against the `type` of the surrounding input — e.g.
+   * `autocomplete="url"` on `<input type="email">` is rejected because
+   * the two sets do not overlap.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/autocomplete-valid.md
+   */
+  "jsx-a11y/autocomplete-valid"?: TtscLintRuleSetting;
+
+  /**
+   * Require keyboard handlers alongside `onClick` on non-interactive
+   * JSX elements so the element is also reachable by keyboard.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/click-events-have-key-events.md
+   */
+  "jsx-a11y/click-events-have-key-events"?: TtscLintRuleSetting;
+
+  /**
+   * Require interactive controls to have an accessible label
+   * (visible text, `aria-label`, or `aria-labelledby`).
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/control-has-associated-label.md
+   */
+  "jsx-a11y/control-has-associated-label"?: TtscLintRuleSetting;
+
+  /**
+   * Reject empty JSX headings (`<h1>{}</h1>`) — assistive
+   * technology cannot announce content that does not exist.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/heading-has-content.md
+   */
+  "jsx-a11y/heading-has-content"?: TtscLintRuleSetting;
+
+  /**
+   * Require `<html>` JSX elements to declare a non-empty `lang`
+   * attribute so screen readers can pick the correct pronunciation.
+   * Largely superseded by `jsx-a11y/lang`, which also validates the
+   * tag value.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/html-has-lang.md
+   */
+  "jsx-a11y/html-has-lang"?: TtscLintRuleSetting;
+
+  /**
+   * Require every `<iframe>` JSX element to declare a non-empty,
+   * unique `title` so assistive tech can announce the embedded
+   * content. Empty strings, booleans, numbers, and `{...spread}`
+   * without a literal title are all flagged.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/iframe-has-title.md
+   */
+  "jsx-a11y/iframe-has-title"?: TtscLintRuleSetting;
+
+  /**
+   * Reject redundant words such as *image*, *photo*, or *picture*
+   * inside the `alt` attribute of an `<img>` — the role already
+   * conveys "this is an image".
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/img-redundant-alt.md
+   */
+  "jsx-a11y/img-redundant-alt"?: TtscLintRuleSetting;
+
+  /**
+   * Require elements with interactive ARIA roles (`role="button"`,
+   * `role="link"`, ...) to be focusable.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/interactive-supports-focus.md
+   */
+  "jsx-a11y/interactive-supports-focus"?: TtscLintRuleSetting;
+
+  /**
+   * Require `<label>` elements to either wrap a form control or
+   * reference one via `htmlFor`.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/label-has-associated-control.md
+   */
+  "jsx-a11y/label-has-associated-control"?: TtscLintRuleSetting;
+
+  /**
+   * Deprecated predecessor of `label-has-associated-control`. Checks
+   * the same nesting / `htmlFor` association requirement and supports
+   * configuring which custom components count as labels. Off in
+   * `recommended`; kept only for legacy configs.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/label-has-for.md
+   */
+  "jsx-a11y/label-has-for"?: TtscLintRuleSetting;
+
+  /**
+   * Require the `<html lang>` value to be a valid IETF BCP-47 tag
+   * (`"en"`, `"en-US"`, ...). Superset of `html-has-lang`, since it
+   * also catches present-but-invalid tags like `lang="foo"`.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/lang.md
+   */
+  "jsx-a11y/lang"?: TtscLintRuleSetting;
+
+  /**
+   * Require `<audio>` and `<video>` elements to provide a `<track
+   * kind="captions">` child.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/media-has-caption.md
+   */
+  "jsx-a11y/media-has-caption"?: TtscLintRuleSetting;
+
+  /**
+   * Require `onMouseOver` / `onMouseOut` handlers to have
+   * `onFocus` / `onBlur` parity so keyboard users get the same
+   * interaction.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/mouse-events-have-key-events.md
+   */
+  "jsx-a11y/mouse-events-have-key-events"?: TtscLintRuleSetting;
+
+  /**
+   * Reject the `accessKey` JSX attribute — it conflicts with
+   * assistive-technology keyboard shortcuts.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-access-key.md
+   */
+  "jsx-a11y/no-access-key"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `aria-hidden` on focusable JSX elements — focus would
+   * land on an element hidden from assistive tech.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-aria-hidden-on-focusable.md
+   */
+  "jsx-a11y/no-aria-hidden-on-focusable"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `autoFocus` / `autofocus` JSX attributes — they steal
+   * focus on page load and disorient keyboard users.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-autofocus.md
+   */
+  "jsx-a11y/no-autofocus"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `<blink>` and `<marquee>` — moving content cannot be
+   * paused and harms users with cognitive or visual impairments
+   * (WCAG 2.2.2). The list is closed: extra elements cannot be added.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-distracting-elements.md
+   */
+  "jsx-a11y/no-distracting-elements"?: TtscLintRuleSetting;
+
+  /**
+   * Reject non-interactive ARIA roles applied to natively
+   * interactive elements (e.g. `<button role="presentation">`).
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-interactive-element-to-noninteractive-role.md
+   */
+  "jsx-a11y/no-interactive-element-to-noninteractive-role"?: TtscLintRuleSetting;
+
+  /**
+   * Reject interaction event handlers (`onClick`, `onKeyDown`)
+   * placed on known non-interactive elements without a role
+   * override.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-noninteractive-element-interactions.md
+   */
+  "jsx-a11y/no-noninteractive-element-interactions"?: TtscLintRuleSetting;
+
+  /**
+   * Reject interactive ARIA roles applied to non-interactive
+   * elements (e.g. `<li role="button">`); use the matching
+   * interactive tag.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-noninteractive-element-to-interactive-role.md
+   */
+  "jsx-a11y/no-noninteractive-element-to-interactive-role"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `tabIndex` on non-interactive JSX elements that have
+   * no interactive role.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-noninteractive-tabindex.md
+   */
+  "jsx-a11y/no-noninteractive-tabindex"?: TtscLintRuleSetting;
+
+  /**
+   * Reject explicit `role` attributes that duplicate the
+   * native semantics of the element (e.g. `<button
+   * role="button">`).
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-redundant-roles.md
+   */
+  "jsx-a11y/no-redundant-roles"?: TtscLintRuleSetting;
+
+  /**
+   * Require static elements with interaction handlers to declare
+   * an interactive `role`.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-static-element-interactions.md
+   */
+  "jsx-a11y/no-static-element-interactions"?: TtscLintRuleSetting;
+
+  /**
+   * Prefer native JSX tags over `div` / `span` plus an equivalent
+   * `role` (e.g. `<button>` over `<div role="button">`).
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/prefer-tag-over-role.md
+   */
+  "jsx-a11y/prefer-tag-over-role"?: TtscLintRuleSetting;
+
+  /**
+   * Require ARIA properties that the chosen role mandates (e.g.
+   * `aria-checked` on `role="checkbox"`).
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/role-has-required-aria-props.md
+   */
+  "jsx-a11y/role-has-required-aria-props"?: TtscLintRuleSetting;
+
+  /**
+   * Reject ARIA properties that the role does not support (e.g.
+   * `aria-checked` on `role="link"`).
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/role-supports-aria-props.md
+   */
+  "jsx-a11y/role-supports-aria-props"?: TtscLintRuleSetting;
+
+  /**
+   * Restrict the `scope` attribute to `<th>` cells. On any other tag
+   * (`<div scope="col">`, `<td scope="row">`) the attribute is ignored
+   * by browsers and confuses table-aware assistive tech.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/scope.md
+   */
+  "jsx-a11y/scope"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `tabIndex` values greater than zero. Positive indices jump
+   * the keyboard focus order out of document order and almost always
+   * desynchronize from later DOM changes; `0` and `-1` remain allowed.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/tabindex-no-positive.md
+   */
+  "jsx-a11y/tabindex-no-positive"?: TtscLintRuleSetting;
+}

package/src/structures/rules/ITtscLintNextjsRules.ts

@@ -0,0 +1,206 @@
+import type { TtscLintRuleSetting } from "../TtscLintRuleSetting";
+
+/**
+ * Next.js framework rules from `@next/eslint-plugin-next`, applied to
+ * TypeScript and TSX sources inside Next.js apps.
+ *
+ * Checks Next.js-specific conventions — pages/app routing, `<Head>`
+ * placement, font and script loading, image and link components —
+ * that the framework's runtime treats as load-bearing.
+ *
+ * @reference https://nextjs.org/docs/app/api-reference/config/eslint
+ */
+export interface ITtscLintNextjsRules {
+  /**
+   * Require a non-blocking `display=` value on Google Fonts
+   * stylesheet links; reject `auto`, `block`, and `fallback`, which
+   * keep text invisible while the font loads and hurt LCP. Prefer
+   * `optional` or `swap`.
+   *
+   * @reference https://nextjs.org/docs/messages/google-font-display
+   */
+  "nextjs/google-font-display"?: TtscLintRuleSetting;
+
+  /**
+   * Require `rel="preconnect"` for `fonts.gstatic.com` links to
+   * shave latency off Google Font fetches.
+   *
+   * @reference https://nextjs.org/docs/messages/google-font-preconnect
+   */
+  "nextjs/google-font-preconnect"?: TtscLintRuleSetting;
+
+  /**
+   * Require an `id` attribute on inline `<Script>` components from
+   * `next/script`.
+   *
+   * Next.js uses the id to track the script across client
+   * navigations and to satisfy its loading-strategy budget; an
+   * inline script without one is silently dropped on subsequent
+   * renders.
+   *
+   * @reference https://nextjs.org/docs/messages/inline-script-id
+   */
+  "nextjs/inline-script-id"?: TtscLintRuleSetting;
+
+  /**
+   * Prefer the Next.js Google Analytics integration over
+   * hand-written `gtag` script tags.
+   *
+   * @reference https://nextjs.org/docs/messages/next-script-for-ga
+   */
+  "nextjs/next-script-for-ga"?: TtscLintRuleSetting;
+
+  /**
+   * Reject local declarations named `module`, which shadow the
+   * CommonJS `module` binding Next.js relies on.
+   *
+   * @reference https://nextjs.org/docs/messages/no-assign-module-variable
+   */
+  "nextjs/no-assign-module-variable"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `async` function bodies on React Client Components.
+   *
+   * The client-side React runtime can't await a component's render,
+   * so an `async` `"use client"` component returns a pending promise
+   * that crashes hydration; do data fetching in a Server Component
+   * or in `useEffect` instead.
+   *
+   * @reference https://nextjs.org/docs/messages/no-async-client-component
+   */
+  "nextjs/no-async-client-component"?: TtscLintRuleSetting;
+
+  /**
+   * Restrict the `next/script` `strategy="beforeInteractive"` option
+   * to `pages/_document.tsx` — anywhere else, the strategy is
+   * downgraded silently.
+   *
+   * @reference https://nextjs.org/docs/messages/no-before-interactive-script-outside-document
+   */
+  "nextjs/no-before-interactive-script-outside-document"?: TtscLintRuleSetting;
+
+  /**
+   * Reject raw `<link rel="stylesheet">` tags.
+   *
+   * Next.js handles CSS through its bundler — imported stylesheets,
+   * CSS Modules, or `next/font` — and manual stylesheet links skip
+   * the runtime's critical-CSS extraction and render-blocking
+   * heuristics.
+   *
+   * @reference https://nextjs.org/docs/messages/no-css-tags
+   */
+  "nextjs/no-css-tags"?: TtscLintRuleSetting;
+
+  /**
+   * Restrict `next/document` imports to `pages/_document.tsx` —
+   * `Document` cannot be used in a regular page.
+   *
+   * @reference https://nextjs.org/docs/messages/no-document-import-in-page
+   */
+  "nextjs/no-document-import-in-page"?: TtscLintRuleSetting;
+
+  /**
+   * Reject more than one `<Head>` element from `next/document` in
+   * `pages/_document.tsx`.
+   *
+   * Next.js merges metadata into the single `<Head>` it renders into
+   * the HTML shell; additional instances are dropped silently and
+   * any tags inside them never reach the page.
+   *
+   * @reference https://nextjs.org/docs/messages/no-duplicate-head
+   */
+  "nextjs/no-duplicate-head"?: TtscLintRuleSetting;
+
+  /**
+   * Reject raw `<head>` elements outside the `app/` directory —
+   * use `next/head` or the metadata exports.
+   *
+   * @reference https://nextjs.org/docs/messages/no-head-element
+   */
+  "nextjs/no-head-element"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `next/head` imports inside `pages/_document.tsx` — use
+   * `next/document`'s `Head` there.
+   *
+   * @reference https://nextjs.org/docs/messages/no-head-import-in-document
+   */
+  "nextjs/no-head-import-in-document"?: TtscLintRuleSetting;
+
+  /**
+   * Prefer `next/link` for internal anchors with a static `href`,
+   * since `Link` performs client-side routing.
+   *
+   * @reference https://nextjs.org/docs/messages/no-html-link-for-pages
+   */
+  "nextjs/no-html-link-for-pages"?: TtscLintRuleSetting;
+
+  /**
+   * Prefer `next/image` over raw `<img>` elements so the framework
+   * can optimize the asset.
+   *
+   * @reference https://nextjs.org/docs/messages/no-img-element
+   */
+  "nextjs/no-img-element"?: TtscLintRuleSetting;
+
+  /**
+   * Reject Google font `<link>` tags inside regular pages files —
+   * load fonts in `_document.tsx` (pages router) or via
+   * `next/font` (app router).
+   *
+   * @reference https://nextjs.org/docs/messages/no-page-custom-font
+   */
+  "nextjs/no-page-custom-font"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `next/script` inside `next/head` — `<Script>` must
+   * appear in the JSX tree, not in `<Head>`.
+   *
+   * @reference https://nextjs.org/docs/messages/no-script-component-in-head
+   */
+  "nextjs/no-script-component-in-head"?: TtscLintRuleSetting;
+
+  /**
+   * Reject styled-jsx tags inside `pages/_document.tsx`, which the
+   * server renders incorrectly.
+   *
+   * @reference https://nextjs.org/docs/messages/no-styled-jsx-in-document
+   */
+  "nextjs/no-styled-jsx-in-document"?: TtscLintRuleSetting;
+
+  /**
+   * Require `async` or `defer` on external raw `<script>` tags so
+   * loading does not block render.
+   *
+   * @reference https://nextjs.org/docs/messages/no-sync-scripts
+   */
+  "nextjs/no-sync-scripts"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `<title>` inside `Head` from `next/document`. Set the
+   * title from the metadata exports instead.
+   *
+   * @reference https://nextjs.org/docs/messages/no-title-in-document-head
+   */
+  "nextjs/no-title-in-document-head"?: TtscLintRuleSetting;
+
+  /**
+   * Catch near-miss typos in Next.js data-fetching export names
+   * (`getStaticProps`, `getStaticPaths`, `getServerSideProps`).
+   *
+   * A misspelled export is treated as ordinary module state, so the
+   * page silently falls back to client-side rendering with no
+   * build-time warning.
+   *
+   * @reference https://nextjs.org/docs/messages/no-typos
+   */
+  "nextjs/no-typos"?: TtscLintRuleSetting;
+
+  /**
+   * Reject Polyfill.io script URLs — Next.js already polyfills
+   * modern browsers, and Polyfill.io has a checkered history.
+   *
+   * @reference https://nextjs.org/docs/messages/no-unwanted-polyfillio
+   */
+  "nextjs/no-unwanted-polyfillio"?: TtscLintRuleSetting;
+}