All Errors

TypeScript requires `/// <reference path="..." />` directives to live before any imports, exports, or executable statements. Drop them farther down the file and the compiler refuses to run, so keep those directives at the very top or move the code into a module that uses imports instead.

MySQL ERROR 1213 occurs when two or more concurrent transactions are waiting for each other to release locks, creating a circular dependency. This is a transactional database lock contention issue that requires application-level retry logic and optimized transaction design to resolve.

This error means TypeScript inferred the bottom type <code>never</code> for a branch or position but you are assigning an <code>any</code> value to it. The compiler rejects it because <code>never</code> explicitly represents no possible values.

TypeScript throws this error when a method is invoked with a `this` binding that does not match its declared `this` parameter (common when methods are extracted or passed as callbacks). Align the call site by keeping the method bound, declaring explicit `this` parameters, or narrowing/binding the callback before invoking.

This error occurs when PostgreSQL cannot convert a text value to the expected data type (integer, boolean, date, UUID, etc.). It means the string contains invalid characters or format for the target type.

This error occurs when scp cannot locate the file or directory you're trying to transfer. Common causes include incorrect file paths, typos, relative path confusion, or the file not existing at the specified location.

This Firebase Authentication error occurs when attempting to set a user's display name with an empty string, null, or undefined value. The fix involves ensuring you always provide a valid non-empty string when setting the displayName property through createUser(), updateUser(), or updateProfile() methods.

This TypeScript configuration error occurs when your output directory (outDir) is nested inside your source root directory (rootDir), which would cause compiled files to overwrite source files. The fix involves adjusting your tsconfig.json to ensure outDir is outside rootDir or using separate directories for source and compiled code.

This error occurs when SCP protocol receives a filename that doesn't match the request, due to OpenSSH security validations or special characters in filenames. It can also happen with paths containing colons or dots that require escaping.

This TypeScript error occurs when trying to import a property that is not exported as a named export, or when there is confusion between namespace and module imports. The error typically appears when using incorrect import syntax for the export type available in the module.

This TypeScript error occurs when using project references and the referenced project has been modified without rebuilding. TypeScript needs to rebuild the referenced project to ensure type information is up-to-date. Running `tsc --build` or `tsc -b` will rebuild all referenced projects.

This TypeScript error occurs when you try to use one function parameter's value to initialize another parameter's default value. TypeScript doesn't allow parameter references in default value expressions because parameters are evaluated in order. The fix involves restructuring your function to use destructuring, optional parameters, or separate initialization logic.

This TypeScript error occurs when a function parameter lacks an explicit type annotation and the 'noImplicitAny' compiler option is enabled. The fix involves adding proper type annotations to parameters, using type inference where appropriate, or adjusting TypeScript configuration.

This error occurs when an SFTP connection is abruptly terminated by the server during transfer. Common causes include chroot directory permission issues, IP blocking from failed attempts, network timeouts, firewall restrictions, or key exchange algorithm mismatches.

The "Failed publickey for user" message appears in sshd logs when an SSH client attempts public key authentication but the server rejects the key. This indicates a mismatch between the client's key and the server's authorized_keys, or the server doesn't recognize the key algorithm.

This error occurs when Supabase Auth rejects a multi-factor authentication (MFA) verification attempt, typically due to invalid codes, rate limiting, or custom verification hooks blocking the authentication flow.

This TypeScript error occurs when you try to use generic type parameters in static class members. Static members exist at the class level, not instance level, so they cannot access instance-specific type parameters. The fix involves restructuring your code to avoid referencing type parameters in static contexts.

This TypeScript error occurs when you try to re-export everything from a module using 'export * from' syntax without specifying what to export. The fix involves using named exports, namespace exports, or adjusting your module structure to properly re-export the desired content.

This TypeScript error occurs when you define both specific properties and an index signature on the same type, making the specific properties unreachable. The index signature acts as a catch-all that overshadows any explicitly defined properties, preventing TypeScript from accessing them safely.

This error occurs when using Prisma Accelerate and the Prisma schema has not been properly synchronized with the Accelerate service. It typically happens during build or deployment when the client is generated before the schema is uploaded to Accelerate.