@formancy/code-style 0.0.0-stage → 0.12.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,4 @@
+formancy
+Copyright 2026 Daniel Bacher
+
+This product includes software developed by the formancy project.

package/README.md

@@ -1,3 +1,106 @@
-# Temporary Holding Version
+<!-- Part of formancy: https://github.com/sharkysan/formancy.ai -->
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+# @formancy/code-style
+
+The lint rules and the format the formancy repositories share: an ESLint
+configuration and Prettier's options, in one JavaScript module that each
+repository calls with its own paths. It names no path of any repository, so
+the repositories hold one set of rules and one style without a copy each.
+
+## Use
+
+```bash
+npm install --save-dev @formancy/code-style eslint prettier typescript
+```
+
+ESLint, Prettier and TypeScript are peers: a repository installs them at
+versions of its own, inside the ranges the manifest declares, each of which
+starts at the version this package's suite runs.
+
+It declares no Node of its own. The Node it runs on is ESLint's, which its
+`eslint` peer and its `@eslint/js` dependency both declare as
+`^20.19.0 || ^22.13.0 || >=24` (ESLint 10.13.0 and `@eslint/js` 10.0.1, read on
+2026-10-30). That is the floor that binds, and it is above the `>=22.12.0`
+formancy.ai's own manifest declares.
+
+`eslint.config.mjs`:
+
+```js
+import { eslintConfig } from '@formancy/code-style'
+
+export default eslintConfig({
+  root: import.meta.dirname,
+  project: ['./packages/*/tsconfig.json'],
+  ignoreFiles: ['.gitignore'],
+  tests: ['**/*.test.{ts,tsx,mjs}'],
+})
+```
+
+`prettier.config.mjs`:
+
+```js
+export { prettierConfig as default } from '@formancy/code-style'
+```
+
+`FILES` is the glob a repository's `format` and `format:check` scripts hand
+Prettier, and `EXTENSIONS` its extensions: TypeScript's and JavaScript's, so
+that neither tool reads a file the other does not.
+
+## The paths a repository passes
+
+The module's doc comment on `eslintConfig` is the reference; in short:
+
+- **`root`**, absolute: the repository, which the other paths are read from.
+- **`project`**: the tsconfigs that type its TypeScript, by glob.
+- **`ignoreFiles`**: its `.gitignore` files, each read for its own directory, as
+  git reads it. Build output, coverage and test results are ignored besides.
+- **`tests`**: its test files, which alone are relaxed.
+- **`untyped`**: TypeScript no tsconfig holds, linted without types.
+- **`browser`**: files that drive a page, which know the page's globals.
+- **`react`**: its React components and hooks.
+
+The first four are required, and a call without one is refused where the
+configuration is made: without `tests`, every file would be relaxed. A
+repository's own exception, such as a generated file, is written where it calls
+this, as a `globalIgnores` beside it and a line in `.prettierignore`, and never
+in the module.
+
+## What it holds
+
+- **The rules** are `@eslint/js`'s recommended set and typescript-eslint's
+  type-aware one, every rule an error or off: a warning is a finding nobody has
+  to fix. A name may go unused only if it begins with `_`. A disable comment
+  says why after `--`, and one that disables nothing is an error. A typographic
+  space is allowed in a string, a template and JSX text, and refused between two
+  tokens. Where `react` points, a hook may not run under a condition or miss a
+  dependency.
+- **A test is relaxed** for the `no-unsafe-*` rules, `no-explicit-any` and `unbound-method`
+  alone, and held to everything else. `require-await` is off in every file: an `async`
+  function with no `await` is how a synchronous implementation of an async contract keeps
+  its throws as rejections, and `no-floating-promises` and `no-misused-promises` still
+  catch a forgotten `await`.
+- **The format** is Prettier's defaults but five: no semicolons, single quotes,
+  trailing commas wherever they are allowed, 160 columns, and code embedded in
+  a string left as written, because an Angular template's whitespace renders.
+
+It ships no type declarations: a repository imports it from a JavaScript
+configuration file. A configuration TypeScript checks with `checkJs` has nothing
+of it typed. Measured with TypeScript 6.0.3 on 2026-10-30: under `noImplicitAny`,
+which `strict` sets, the import is error TS7016, a module with no declaration
+file; without it, every name imported is `any`, so a misspelled option passes the
+check, and a required path left out is refused only when ESLint loads the
+configuration.
+
+## Where it comes from
+
+The module and its test, `src/code-style.mjs` and `src/code-style.test.mjs`,
+were written for Formancy Health (formancy.ai-health 0017) and are carried here
+byte for byte; the repositories that copied them pin this package in their place
+once it is released. The test is this package's suite. It lints a repository of
+its own, written to the system's temporary directory, and holds that each rule
+runs at error on the kind of file it is for and that each path does what it
+says. It does not hold that what a rule reports is a defect.
+
+`pnpm test:e2e:install` installs the packed tarball with its dependencies and
+peers into a project outside the workspace, and lints and formats a file there
+with it.

package/package.json

@@ -1,6 +1,64 @@
 {
   "name": "@formancy/code-style",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
+  "version": "0.12.0",
+  "description": "The ESLint rules and the Prettier format the formancy repositories share: one module, which each repository calls with its own paths.",
+  "license": "Apache-2.0",
+  "type": "module",
+  "sideEffects": false,
+  "exports": {
+    ".": "./src/code-style.mjs"
+  },
+  "files": [
+    "src/code-style.mjs",
+    "LICENSE",
+    "NOTICE"
+  ],
+  "//check:pkg": [
+    "publint only, as for @formancy/themes: this package ships one JavaScript module",
+    "and no types, so there is nothing for attw to resolve. Nothing here builds or",
+    "type-checks either: the module is published as it is written, byte for byte the",
+    "copy formancy.ai-health and formancy.ai-data carry until they pin this package."
+  ],
+  "dependencies": {
+    "@eslint-community/eslint-plugin-eslint-comments": "^4.8.1",
+    "@eslint/js": "^10.0.1",
+    "eslint-plugin-react-hooks": "^7.1.1",
+    "globals": "^17.13.0",
+    "typescript-eslint": "^8.72.1"
+  },
+  "peerDependencies": {
+    "eslint": "^10.13.0",
+    "prettier": "^3.9.10",
+    "typescript": "~6.0.3"
+  },
+  "//peerDependencies": [
+    "The tools a repository runs, at versions it chooses, so they are peers. Each",
+    "range starts at the version this package's suite runs, which the workspace",
+    "catalog pins exactly, and the install gate installs the newest each admits: the",
+    "bound of a range is a version something ran (0134). TypeScript's is the",
+    "catalog's own range, for 0039's reason; typescript-eslint asks for it."
+  ],
+  "devDependencies": {
+    "@vitest/coverage-v8": "^5.0.1",
+    "eslint": "10.13.0",
+    "prettier": "3.9.10",
+    "publint": "^0.3.24",
+    "typescript": "~6.0.3",
+    "vitest": "^5.0.1"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/sharkysan/formancy.ai.git",
+    "directory": "packages/code-style"
+  },
+  "homepage": "https://github.com/sharkysan/formancy.ai",
+  "bugs": "https://github.com/sharkysan/formancy.ai/issues",
+  "scripts": {
+    "test:coverage": "vitest run --coverage",
+    "test": "vitest run",
+    "check:pkg": "publint"
+  }
 }

package/src/code-style.mjs

@@ -0,0 +1,192 @@
+import eslintComments from '@eslint-community/eslint-plugin-eslint-comments/configs'
+import js from '@eslint/js'
+import { defineConfig, includeIgnoreFile } from 'eslint/config'
+import reactHooks from 'eslint-plugin-react-hooks'
+import globals from 'globals'
+import { isAbsolute, resolve } from 'node:path'
+import tseslint from 'typescript-eslint'
+
+/**
+ * The lint rules and the format the four formancy repositories share: what
+ * formancy.ai will publish as `@formancy/code-style`, and until then this
+ * file, copied byte for byte into each repository, which calls it with its
+ * own paths and pins the package in its place once it is released
+ * (formancy.ai-health 0017). Nothing here names a path of one repository;
+ * a reason that holds for one alone is written where that one calls it.
+ *
+ * The rules are @eslint/js's recommended set and typescript-eslint's
+ * type-aware one, every rule `error` or `off`: a warning is a finding
+ * nobody has to fix. `code-style.test.mjs`, beside this file, holds what
+ * each rule and each path does; a repository's own guard holds what it
+ * passes, and that every file it holds is linted and formatted by them.
+ */
+
+const TYPESCRIPT = ['ts', 'tsx', 'mts', 'cts']
+const JAVASCRIPT = ['js', 'jsx', 'mjs', 'cjs']
+const filesOf = (extensions) => `**/*.{${extensions.join(',')}}`
+
+/**
+ * TypeScript's extensions, then JavaScript's: every file ESLint lints and
+ * Prettier formats, one list, so that neither reads a file the other does
+ * not.
+ */
+export const EXTENSIONS = [...TYPESCRIPT, ...JAVASCRIPT]
+
+/** The same, as the glob a repository's `format` and `format:check` scripts hand Prettier. */
+export const FILES = filesOf(EXTENSIONS)
+
+/**
+ * Prettier's options, and its defaults otherwise. Of the widths measured,
+ * 160 columns rewrote the fewest lines (formancy.ai-health 0017), and one
+ * width across the four repositories is the point. Code embedded in a
+ * string is left as written: Prettier reflowed an Angular component's
+ * inline template, whose whitespace renders (formancy.ai-health 0017).
+ */
+export const prettierConfig = { semi: false, singleQuote: true, trailingComma: 'all', printWidth: 160, embeddedLanguageFormatting: 'off' }
+
+/**
+ * Unused names fail unless they begin with `_` -- arguments, variables,
+ * caught errors, destructured array elements -- the convention the
+ * repositories already had. Both base sets name an unused-variable rule;
+ * typescript-eslint's recommended set turns @eslint/js's off, in
+ * JavaScript as in TypeScript, so there is one rule and one report per
+ * finding.
+ */
+const UNUSED_NAMES = {
+  args: 'all',
+  argsIgnorePattern: '^_',
+  vars: 'all',
+  varsIgnorePattern: '^_',
+  caughtErrors: 'all',
+  caughtErrorsIgnorePattern: '^_',
+  destructuredArrayIgnorePattern: '^_',
+}
+
+/**
+ * Off in a test alone: a test reads an untyped body on purpose, and vitest
+ * is handed methods to `expect`. `no-explicit-any` is off there for the same
+ * reason as the `no-unsafe-*` family: a test types the untyped body it
+ * reads as `any` (seven disables in formancy.ai-data's lint fixes quoted it
+ * word for word); source is still held to it. Nothing else is relaxed, and
+ * test support -- a corpus, a package's test helpers -- is held to every
+ * rule.
+ */
+const TEST_RELAXATIONS = {
+  '@typescript-eslint/no-unsafe-assignment': 'off',
+  '@typescript-eslint/no-unsafe-member-access': 'off',
+  '@typescript-eslint/no-unsafe-call': 'off',
+  '@typescript-eslint/no-unsafe-argument': 'off',
+  '@typescript-eslint/no-unsafe-return': 'off',
+  '@typescript-eslint/unbound-method': 'off',
+  '@typescript-eslint/no-explicit-any': 'off',
+}
+
+/**
+ * `only-throw-error` allows throwing a value typed `any` or `unknown` by
+ * default, and rejecting with the same forwarded value is the same act, so
+ * `prefer-promise-reject-errors` allows it too, everywhere: a signal's
+ * `reason`, a driver's rejection passed on (nine disable comments in
+ * formancy.ai-data's lint fixes gave exactly that reason). A rejection with
+ * a known non-Error value, a string or object literal, is still refused.
+ */
+const REJECT_ERRORS = ['error', { allowThrowingAny: true, allowThrowingUnknown: true }]
+
+/**
+ * `require-await` is off everywhere, not in tests alone: an `async` function
+ * with no `await` is how a synchronous implementation of an asynchronous
+ * contract keeps its throws as rejections, and the rule cannot tell that
+ * from an `async` left behind by a refactor. Every repository met it where
+ * the contract is async and the body is not. formancy.ai-data, measured on
+ * 30 October 2026: 220 findings, 201 of them in tests (`fetch: async () =>
+ * new Response(...)`, `readFile: async (p) => ...`), the other 19 Fastify
+ * handlers and hooks and test support. formancy.ai, the same day: 68
+ * findings left after every other rule was fixed, all in test-support
+ * implementations of Promise-returning ports outside test files, each of
+ * which throws, so that `async` gives the rejection the real port gives and
+ * `Promise.resolve` would change what the code under test meets. A forgotten
+ * `await` is still caught by `no-floating-promises` and
+ * `no-misused-promises`; what is no longer reported anywhere is a pointless
+ * `async` a refactor left behind.
+ */
+const NO_REQUIRE_AWAIT = 'off'
+
+/**
+ * The ESLint configuration for one repository, given its paths:
+ *
+ * - `root`, absolute: the repository, which the other paths are read from;
+ * - `project`: the tsconfigs that type its TypeScript, by glob -- those its
+ *   typecheck runs, so that a package added is linted with types without
+ *   an edit;
+ * - `ignoreFiles`: its `.gitignore` files, each read for its own directory,
+ *   as git reads it; build output, coverage and test results are ignored
+ *   besides;
+ * - `tests`: its test files, which alone are relaxed;
+ * - `untyped`: TypeScript that none of its tsconfigs holds, linted without
+ *   types as JavaScript is;
+ * - `browser`: files that drive a page, whose callbacks run there, and know
+ *   the page's globals beside Node's;
+ * - `react`: its React components and hooks.
+ *
+ * The first four are required: one left out would lint otherwise than the
+ * repository holds -- without `tests`, every file would be relaxed -- so it
+ * is refused here. The last three may be empty.
+ */
+export function eslintConfig({ root, project, ignoreFiles, tests, untyped = [], browser = [], react = [] }) {
+  if (typeof root !== 'string' || !isAbsolute(root)) throw new TypeError('code-style: root must be an absolute path')
+  for (const [name, globs] of Object.entries({ project, ignoreFiles, tests })) {
+    if (!Array.isArray(globs) || globs.length === 0) throw new TypeError(`code-style: ${name} must name at least one path`)
+  }
+  return defineConfig(
+    includeIgnoreFile(
+      ignoreFiles.map((file) => resolve(root, file)),
+      { gitignoreResolution: true },
+    ),
+    { ignores: ['**/dist/**', '**/coverage/**', '**/test-results/**'] },
+    {
+      linterOptions: { reportUnusedDisableDirectives: 'error', reportUnusedInlineConfigs: 'error' },
+    },
+    {
+      // typescript-eslint's documented pairing: its type-aware set on every
+      // file, and its typed half turned off below where nothing types the
+      // file, so that JavaScript is held to its rules that need no types --
+      // an expression whose value is dropped, an assertion missing its call
+      // among them -- as TypeScript is. Its overrides of @eslint/js's rules
+      // that the compiler holds apply to TypeScript alone.
+      files: [FILES],
+      extends: [js.configs.recommended, tseslint.configs.recommendedTypeChecked],
+      languageOptions: { parserOptions: { project, tsconfigRootDir: root } },
+      rules: {
+        '@typescript-eslint/no-unused-vars': ['error', UNUSED_NAMES],
+        '@typescript-eslint/prefer-promise-reject-errors': REJECT_ERRORS,
+        '@typescript-eslint/require-await': NO_REQUIRE_AWAIT,
+      },
+    },
+    {
+      // JavaScript, and TypeScript that no tsconfig holds, are linted without
+      // types, and run in Node: no-undef stays on for JavaScript, and is
+      // what is left to catch a misspelt name in a script before the one run
+      // that reaches it fails.
+      files: [filesOf(JAVASCRIPT), ...untyped],
+      extends: [tseslint.configs.disableTypeChecked],
+      languageOptions: { globals: globals.node },
+    },
+    // A page.evaluate callback runs in the page.
+    ...(browser.length === 0 ? [] : [{ files: browser, languageOptions: { globals: { ...globals.node, ...globals.browser } } }]),
+    {
+      // The products speak several languages, whose typography puts narrow
+      // spaces in strings and templates; between two tokens of code the
+      // same character is an invisible bug.
+      rules: { 'no-irregular-whitespace': ['error', { skipStrings: true, skipTemplates: true, skipJSXText: true }] },
+    },
+    // The two rules a hook's caller breaks, and not react-hooks 7's whole
+    // recommended set, which adds the React Compiler's.
+    ...(react.length === 0
+      ? []
+      : [{ files: react, plugins: { 'react-hooks': reactHooks }, rules: { 'react-hooks/rules-of-hooks': 'error', 'react-hooks/exhaustive-deps': 'error' } }]),
+    // A disable comment says why, after `--`: a bare one hides a finding
+    // without a reason. One that disables nothing is an error above.
+    eslintComments.recommended,
+    { rules: { '@eslint-community/eslint-comments/require-description': 'error' } },
+    { files: tests, rules: TEST_RELAXATIONS },
+  )
+}