All Errors

TypeScript raises this diagnostic when a file that already declares itself as a module still tries to pull in another module using `/// <reference ... />`. Triple-slash directives belong to legacy script ordering and are incompatible with ES module imports, so the compiler refuses to emit the file.

TypeScript throws this error whenever a `/// <reference path="…" />` directive points at a route the compiler cannot resolve. The directive has to reference an actual `.ts`/`.d.ts` file inside the project roots, so typos, missing files, or going outside `rootDir` will surface the message.

The Prisma P3007 error occurs when you try to use preview features in your Prisma schema that are not yet supported by the schema engine for migrations. This typically happens when using experimental features that require specific Prisma versions or configuration. The fix involves removing unsupported preview features or updating your Prisma setup.

TS2536 happens when you try to read or write a property with a broad `string | number` union but the target type only exposes named members or lacks a matching index signature.

Triple-slash directives let an outFile or pre-compiled bundle control the ordering of files. When those directives reference each other in a loop, TypeScript cannot decide which file should be emitted first and it stops with this diagnostic.

The TypeScript compiler only allows you to specify a custom tsBuildInfoFile when incremental or composite compilation is active. This error pops up whenever you try to cache compilation metadata without enabling either of those modes.

TypeScript refuses to compile when a triple-slash `types` directive appears inside a file but the compiler is still checking library declaration files. The directive is only permitted when `skipLibCheck` is turned on, so the fix is either to drop the directive or to let the compiler skip library checking

This compiler error means a template literal type is trying to interpolate a placeholder whose type is too broad—usually just `string` or `any`. Template literal placeholders only resolve when they are literal string unions, so the fix is to feed the template a finite set of string literals instead of a wide type.

TypeScript emits this error when a template literal placeholder resolves to another template literal type (often via `keyof T` or a mapped alias) and the compiler cannot treat it as a flattened string union. You can fix it by expanding the inner union, narrowing the placeholder to primitives, or using helper inference to rebuild the string.

You get this error when TypeScript expects a constructor or class reference, but the polymorphic `this` instance type is supplied instead.

This error occurs when you attempt to perform a backup control plane operation (create, delete, or restore) on a DynamoDB backup that is already involved in another operation. Wait for the current operation to complete before retrying.

The TypeScript compiler is telling you that it cannot compile anything because you either ran `tsc` without a tsconfig/project or you pointed it at files that are not TypeScript sources.

A RESTRICT violation occurs when you try to delete or update a parent table row that is still referenced by rows in a child table with a RESTRICT foreign key constraint. The fix requires handling the referencing child rows first or modifying the constraint definition.

This error occurs when Prisma attempts to create a database that already exists on your database server. Learn how to resolve conflicts and properly initialize your database schema.

TypeScript emits this error when a module or global augmentation tries to redeclare a symbol that already exists with a conflicting shape, typically while extending third-party type definitions or maintaining multiple .d.ts files.

The P3000 error occurs when Prisma Migrate fails to create a database during schema deployment. This typically happens due to connection issues, insufficient permissions, or database conflicts. The error includes specific database error details that help diagnose the root cause.

TypeScript shows this error when you try to call `new this()` while `this` still refers to the current instance. Move the factory into a static method or cast the constructor side so that `this` has a construct signature.

TS2683 fires when strict mode or the `noImplicitThis` compiler option is on and the compiler cannot infer a `this` type. Annotating `this`, keeping the lexical context (arrow functions), or binding callbacks gives the compiler the missing context so the error disappears.

This error occurs when a PostgreSQL client attempts to connect to a database but fails to provide authentication credentials. It happens when the user lacks a password, the .pgpass file is misconfigured, or environment variables aren't set properly.

The TypeScript compiler emits TS2538 when a type that could include non-PropertyKey values is used for an index signature or mapped type. Narrowing the key type so it extends PropertyKey (string | number | symbol) restores the mapping.