All Errors

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.

Node.js throws a ModuleNotFoundError when it cannot locate a required module in the node_modules directory or module resolution paths. This typically happens when a package is not installed or the import path is incorrect.

This error occurs when attempting to use require() to import an ES module in a CommonJS context. Node.js enforces strict module system boundaries, and ES modules must be imported using import statements or dynamic import().

This error occurs when attempting to use __dirname or __filename in ES modules. These CommonJS globals are not available in ES module scope, requiring alternative approaches using import.meta.url or the newer import.meta.dirname.

This TypeScript error occurs when you use a type assertion (as) to cast a value to a type that conflicts with type narrowing already performed. TypeScript detects that your assertion contradicts what it has already inferred or narrowed the type to be. The fix involves either removing the unnecessary assertion or adjusting your code flow to work with the narrowed type.

This error occurs when a cryptographic key derivation operation fails in Node.js, typically affecting password hashing functions like pbkdf2, scrypt, or bcrypt. The failure usually stems from invalid parameters, resource constraints, or missing native module support.

npm displays a warning when an optional dependency cannot be installed due to platform incompatibility or build failures. This is informational and does not prevent your project from working.