renovate.json (1)

15-19: Good Renovate grouping for ESLint; consider including Prettier integrations (optional)

Grouping eslint with @eslint/* is correct and matches Renovate’s supported wildcards (as learned previously). Optionally, you may want to group eslint-config-prettier and eslint-plugin-prettier with ESLint updates, since they often move in tandem.

Apply this if you want them grouped together:

     {
       "groupName": "ESLint and its core modules",
-      "matchPackageNames": ["eslint", "@eslint/*"]
+      "matchPackageNames": ["eslint", "@eslint/*", "eslint-config-prettier", "eslint-plugin-prettier"]
     }

eslint.config.ts (3)

20-35: Type it readonly and avoid false positives for node: built-ins

• Minor: prefer ReadonlyArray to prevent accidental mutation.
• Important: builtinModules typically includes both "fs" and "node:fs". Current selector would also flag correct imports like import 'node:fs' and suggest node:node:fs. Filter out the node: prefixed items.

Apply both in one go:

-const importConcerns: RestrictedSyntax[] = [
+const importConcerns: ReadonlyArray<RestrictedSyntax> = [
   {
     selector:
       "ImportDeclaration[source.value='ramda'] > ImportSpecifier, " +
       "ImportDeclaration[source.value='ramda'] > ImportDefaultSpecifier",
     message: "use import * as R from 'ramda'",
   },
   {
     selector: "ImportDeclaration[source.value=/^zod/] > ImportDefaultSpecifier",
     message: "do import { z } instead",
   },
-  ...builtinModules.map((mod) => ({
+  ...builtinModules
+    .filter((mod) => !mod.startsWith("node:"))
+    .map((mod) => ({
       selector: `ImportDeclaration[source.value='${mod}']`,
       message: `use node:${mod} for the built-in module`,
-  })),
+    })),
 ];

---

37-64: Nit: use ReadonlyArray typing for consistency and safety

Same reasoning as above—mark as read-only to avoid accidental mutations during future edits.

-const performanceConcerns: RestrictedSyntax[] = [
+const performanceConcerns: ReadonlyArray<RestrictedSyntax> = [

---

66-168: Mark tsFactoryConcerns as ReadonlyArray and sanity-check selectors

• Change the declaration to prevent accidental mutation while still allowing spread into rules:

-const tsFactoryConcerns: RestrictedSyntax[] = [
+const tsFactoryConcerns: ReadonlyArray<RestrictedSyntax> = [

• No code mutates this array, and ReadonlyArray still supports spread usage at line 242.

– After upgrading ESLint/TS-ESLint, spot-check a few selectors (e.g. Identifier[name='KeyOfKeyword'], Literal[value='Promise']) against the AST emitted by @typescript-eslint/parser. A quick sample .ts file run through your config will confirm they still fire as expected.

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

Learnt from: RobinTail
PR: RobinTail/express-zod-api#2736
File: express-zod-api/tsup.config.ts:12-26
Timestamp: 2025-06-14T16:42:52.972Z
Learning: In express-zod-api tsup configurations, the direct mutation of `options.supported` in the `esbuildOptions` callback is intentional behavior and should not be flagged as a side effect issue.

Learnt from: RobinTail
PR: RobinTail/express-zod-api#0
File: :0-0
Timestamp: 2025-08-01T09:48:13.742Z
Learning: In express-zod-api, when migrating from Zod v3 to v4, the correct approach for internal type imports is to change from `import type { $ZodType } from "zod/v4/core"` to `import { z } from "zod"` and then use `z.core.$ZodType`. The zod/v4/core module is reexported as z.core by the main zod package, making this a valid and working approach.

Learnt from: RobinTail
PR: RobinTail/express-zod-api#2697
File: CHANGELOG.md:5-5
Timestamp: 2025-06-02T21:08:56.475Z
Learning: The `cjs-test` directory in the express-zod-api repository is a test workspace and should be excluded when checking for main project version consistency with changelog entries.

Learnt from: RobinTail
PR: RobinTail/express-zod-api#2428
File: express-zod-api/src/index.ts:44-44
Timestamp: 2025-05-28T18:58:10.064Z
Learning: The type-only import `import type {} from "qs";` in express-zod-api/src/index.ts is necessary to avoid TS2742 errors for exported functions like attachRouting, makeRequestMock, testEndpoint, and testMiddleware that have types depending on types/qs. This import provides the reference TypeScript needs to infer portable type names.

Learnt from: RobinTail
PR: RobinTail/express-zod-api#2746
File: renovate.json:6-13
Timestamp: 2025-06-15T13:56:19.544Z
Learning: In Renovate configuration, `matchPackageNames` supports wildcard patterns using glob syntax (e.g., `typescript-eslint/*`). There is no `matchPackagePatterns` field. The `groupName` property is required to group related packages into single PRs.