All Errors

This error occurs when attempting to set HTTP headers with invalid characters, such as control characters, newlines, or improperly encoded non-ASCII text. Node.js enforces strict HTTP header validation to prevent security vulnerabilities.

This error occurs when you try to run an npm script that is not defined in the scripts section of your package.json file. npm cannot execute a script it cannot find.

This error occurs when you pass an invalid entry type to PerformanceObserver.observe() in Node.js's perf_hooks module. The observer only accepts specific, predefined entry types.

This TypeError occurs when you pass a non-string value to path.parse(), most commonly undefined, null, or a Buffer. The path module's parse() method strictly requires a string argument to extract path components.

The setgid EPERM error occurs when a Node.js process attempts to change its group ID without sufficient privileges. This commonly happens when setuid() is called before setgid(), or when the process lacks CAP_SETGID capability.

This error occurs when an application or package requires a specific Node.js version, but a different version is currently running. Common in projects with strict version requirements or when switching between projects with different Node.js dependencies.

This error occurs when implementing a custom writable stream without properly defining the required _write() method. Node.js expects all custom writable streams to implement this internal method to handle data processing.

This error occurs when passing a non-string value as the separator parameter to querystring.parse() or querystring.stringify(). The querystring module requires separator and assignment parameters to be strings, not null, undefined, numbers, or other types.

This error occurs when creating a custom Readable stream class without implementing the required _read() method. Node.js expects all custom Readable streams to define how data is generated and pushed to consumers.

This error occurs when a Node.js client attempts to connect to a server using incompatible TLS/SSL protocol versions. The TLS handshake fails because the client and server cannot agree on a mutually supported protocol version.

This TypeScript error (TS2304) occurs when using CommonJS exports without proper configuration. The fix involves installing @types/node, configuring tsconfig.json with CommonJS module settings, or using proper ES module syntax.

This TypeScript error occurs when you try to use 'undefined' as a variable name or reference it in a way TypeScript doesn't recognize. The fix involves understanding how undefined works in TypeScript and using proper type annotations instead of treating it as a named variable.

This TypeScript error occurs when you try to use the require() function without proper type definitions. The fix involves installing @types/node, configuring your tsconfig.json, or switching to ES6 imports depending on your project setup.

This error occurs when TypeScript's type inference cannot determine the type of a variable within a conditional type clause. The fix typically involves providing explicit type hints or restructuring the conditional type to give TypeScript enough information to infer the type.

This error occurs when Node.js cannot find any valid cipher suites for establishing a TLS/SSL connection, typically due to invalid cipher configuration, security level conflicts, or incompatible cipher specifications.

This error occurs when a TLS client attempts to use session resumption via session tickets, but the server has explicitly disabled this feature through the SSL_OP_NO_TICKET flag. Session tickets are a performance optimization that allows clients to resume previous TLS sessions without a full handshake.

The Z_DATA_ERROR occurs when Node.js zlib detects corrupted or invalid compressed data during decompression. This typically happens when attempting to decompress data with incorrect headers, truncated content, or using the wrong decompression method.

This error occurs when attempting to verify a JSON Web Token (JWT) that has passed its expiration time. The jsonwebtoken library throws a TokenExpiredError when the token's exp claim indicates it is no longer valid.

This error occurs when an HTTP client follows too many redirect responses, exceeding the configured limit. It commonly happens with axios, node-fetch, or the follow-redirects package when a server creates a redirect loop or when legitimate redirects exceed the maxRedirects threshold (default 21).

This error occurs when Node.js cannot load a compiled native addon module from the expected build directory. Native modules are C++ extensions that must be compiled for your specific platform and Node.js version.