All Errors

SQLSTATE 22009 occurs when PostgreSQL encounters an invalid time zone offset or displacement value. This error typically appears when working with time zone-aware timestamps, interval arithmetic, or when converting between time zones with malformed offset values.

This error occurs when using React Testing Library's queryBy* methods with async assertions like waitFor or findBy*. queryBy* queries are designed for synchronous checks and return null when elements aren't found, while findBy* and getBy* queries handle async operations properly. Understanding the difference between query types prevents this common testing mistake.

This error occurs when PostgreSQL rejects a login attempt due to incorrect credentials, misconfigured authentication settings, or a missing password. Common causes include wrong password, incorrect pg_hba.conf authentication method, or users created without passwords.

Supabase Auth rejects an email address during signup or authentication due to format validation rules. This typically occurs when the email format violates Supabase's validation requirements, which may be stricter than standard RFC 5322 specifications.

This TypeScript error occurs when you try to import a module using default import syntax (import X from "module"), but the module only exports named exports. The fix involves changing your import syntax to use named imports or modifying the module to include a default export.

This TypeScript error occurs when trying to import a default export from a module that doesn't have one. The module might use named exports instead, or the export configuration may be incorrect. Fixes include using named imports, checking module's export structure, or configuring esModuleInterop.

This error occurs when PostgreSQL cannot determine whether a transaction was committed or rolled back due to a connection loss. It typically indicates a network disruption between your application and the database server.

This PostgreSQL error occurs when attempting to insert a duplicate value into a column with a unique constraint in your Supabase database. The constraint could be a primary key, unique index, or explicitly defined unique column.

This TypeScript configuration error occurs when you try to use the modern 'esnext' module system with legacy JavaScript targets (ES3 or ES5). The esnext module format requires modern JavaScript features that aren't available in older ECMAScript versions. To fix this, either upgrade your target to ES2015+ or switch to a compatible module system like CommonJS.

This TypeScript error occurs when you declare a namespace without providing a name. Namespaces help organize code into logical groups and prevent naming collisions. The fix involves adding a valid identifier after the "namespace" keyword.

This error occurs when you attempt to connect to PostgreSQL while it is still initializing or recovering from an unexpected shutdown. Typically, waiting for the startup process to complete or restarting the database service resolves the issue.

The ioredis 'Command timed out' error occurs when a Redis command fails to return a response within the configured timeout period. This typically indicates network issues, slow Redis operations, or insufficient timeout configuration.

This TypeScript error occurs when you have multiple namespace declarations with conflicting structures. It typically happens when merging namespaces from different files or when type definitions have incompatible members. The fix involves ensuring consistent namespace structure across all declarations.

This TypeScript error occurs when you try to redeclare a namespace in an ambient context (like in a .d.ts file). The fix involves understanding ambient declarations, using proper module augmentation patterns, or converting ambient declarations to modules.

Supabase Auth returns the "bad_json" error when the HTTP request body sent to authentication endpoints contains malformed JSON or cannot be parsed. This error prevents authentication operations like sign-up, sign-in, or token refresh and requires fixing the JSON payload structure before retrying.

This TypeScript error (TS2305) occurs when you try to import a named export that doesn't exist in the module. Common causes include typos in import names, incorrect export statements, or version mismatches between packages. The fix involves verifying the correct export names and ensuring proper module structure.

This TypeScript configuration error occurs when an invalid value is set for the moduleResolution compiler option in tsconfig.json. The fix involves correcting the moduleResolution value to one of the valid options: 'node', 'node16', 'nodenext', 'classic', or 'bundler'.

This TypeScript error occurs when nested conditional types create impossible type combinations that resolve to the 'never' type. The fix involves simplifying complex type logic, using distributive conditional types, or restructuring type definitions to avoid infinite recursion or impossible constraints.

This error occurs when ts-node tries to load an ES module (ESM) using CommonJS require(). It happens when mixing module systems, typically when a package uses ESM exports but your tsconfig.json or runtime expects CommonJS. The fix involves aligning module systems across your configuration.

This error occurs when PostgreSQL terminates a connection abnormally, typically due to server crashes, network issues, idle timeouts, or firewall interference. Fix it by checking server logs, adjusting TCP keepalive settings, and configuring proper timeout values.