TypeORM 1

Apply the Node.js 24, TypeScript 7, and JavaScript ES2026 prompts first. These rules target TypeORM 1 and were checked against 1.1.0, which requires Node.js 24.11.0 or later on the 24 line. Apply relational SQL rules to SQL drivers and the MongoDB-specific rules when using MongoRepository.

Runtime and configuration

• Use a maintained Node.js 24 patch meeting TypeORM's minimum and a patched database driver within 1.1.0's peer dependency range. Use mysql2 for MySQL/MariaDB and better-sqlite3 for Node SQLite; the old mysql and sqlite3 integrations were removed in v1.
• Construct DataSource options from validated server configuration. Do not rely on automatic .env loading or legacy TYPEORM_* configuration, which v1 removed; explicitly supply the intended database and fail startup if required settings are missing.
• Keep entities, subscribers, migrations, naming strategies, and CLI data-source paths under deployment control. Their classes, module paths, glob matches, and schema expressions are executable configuration; never derive them from request data or scan upload directories.
• Review the effective native-driver options in extra, including overrides of TLS, timeouts, pooling, and logging. TypeORM passes this object to the driver without validating its driver-specific keys or values.

Criteria and authorization

• Preserve invalidWhereValuesBehavior: { null: "throw", undefined: "throw" }, the 1.1.0 defaults, and use IsNull() for intentional SQL null matching. Do not restore "ignore" to accommodate malformed filters because it removes