All Errors

This TypeScript error occurs when you attempt to invoke a value that doesn't have a call signature—essentially trying to call something that isn't a function. Common causes include calling non-function types, incorrect imports, type mismatches, and union types that confuse the compiler.

This warning appears when more than 10 event listeners are attached to a single EventEmitter instance, indicating a potential memory leak from listeners not being properly cleaned up.

This error occurs when an asynchronous operation exceeds its configured time limit without completing. Common in network requests, database queries, and long-running async operations.

This TypeScript error occurs when you try to assign a value to a variable or array that TypeScript has inferred as the 'never' type. This commonly happens with empty arrays, exhaustive type narrowing, or incorrect type annotations. The fix involves providing explicit type annotations or adjusting your code logic.

This TypeScript error (TS4023) occurs when generating declaration files and the compiler cannot properly reference types from external modules in your exported variables. It happens when you export a variable whose inferred type uses types from external modules that cannot be explicitly named in the generated .d.ts file.

This TypeScript error occurs when you attempt to use an invalid expression or operation within a template literal type definition. Template literal types only allow specific type-level constructs like type parameters, unions, and intrinsic string manipulation types, not runtime expressions or complex type operations.

This error occurs when a network request does not complete within the specified time limit and the socket connection times out. It commonly happens with HTTP clients when the server takes too long to respond or network connectivity issues prevent timely communication.

This TypeScript error occurs when a non-abstract (concrete) class extends an abstract base class but fails to implement all abstract members. All classes that extend abstract classes must either implement every abstract method and property, or be declared abstract themselves.

This error occurs when Docker Desktop on Windows is set to run Windows containers, but you're trying to pull or run a Linux-based image. Switching Docker Desktop to Linux containers mode will resolve the issue.

This error occurs when Docker encounters an unrecognized instruction in your Dockerfile, typically due to a typo like 'RRUN' instead of 'RUN'. Fixing the typo in your Dockerfile will resolve the issue immediately.

This error occurs when you try to access a property or function from a module that was not properly exported, or when module.exports is assigned inside a callback. It commonly happens when mixing CommonJS and ES Module syntax or importing non-existent named exports.

This error occurs when attempting to access a property on a variable that is undefined or null. It is one of the most common runtime errors in Node.js and JavaScript, typically caused by accessing data before it is initialized or when API responses are missing expected fields.

This error occurs when you try to start a Node.js server on a port that is already occupied by another process. The system refuses to bind to the port because another application is already listening on it.

This error occurs when a TCP connection is forcibly closed by the remote server or network device before your Node.js application finishes reading data. The connection is abruptly terminated by sending a TCP RST packet instead of a graceful close.

This error occurs when the crypto.createHmac() method receives a key argument that is not a valid type. Node.js requires the HMAC key to be a string, Buffer, TypedArray, DataView, or KeyObject, and passing undefined, null, or other invalid types will cause this error.

This system-level error occurs when attempting to initiate a network operation (like a socket connection) that is already in progress. It commonly happens when reconnecting sockets too quickly or trying to bind resources that are already being accessed.

This error occurs when Node.js attempts to establish a TCP connection but the operating system cannot find a network route to the destination. The connection fails because no routing path exists between your system and the target host.

This error occurs when you attempt to call a value as a function, but that value is not actually a function. It commonly happens due to typos in function names, calling properties that hold non-function values, or issues with module loading and scope.

This Node.js error occurs when the operating system blocks a file system operation due to insufficient permissions, file locking by another process, or security restrictions. Common scenarios include writing to protected directories, accessing files opened by other applications, or operating on files locked by antivirus software.

This error occurs when Node.js file system operations attempt to read, write, or manipulate a directory as if it were a regular file. The operation expects a file path but receives a directory path instead.