@pnpm/error 1100.1.4 → 1100.2.1

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @pnpm/error
 
+## 1100.2.1
+
+### Patch Changes
+
+- `pnpm install` now works in StackBlitz WebContainers on projects without a lockfile. It used to fail there with `ENOENT ... pnpm-lock.yaml`, because pnpm did not recognize the errors that WebContainers return from asynchronous file system calls [#15649](https://github.com/pnpm/pnpm/issues/15649).
+
+## 1100.2.0
+
+### Minor Changes
+
+- When the registry stops sending data for longer than `fetchTimeout`, pnpm now reports that the metadata or tarball request timed out. Previously the error did not mention the timeout [#3646](https://github.com/pnpm/pnpm/issues/3646).
+
 ## 1100.1.4
 
 ### Patch Changes

package/lib/index.d.ts

@@ -27,6 +27,17 @@ export declare class FetchError extends PnpmError {
     readonly request: FetchErrorRequest;
     constructor(request: FetchErrorRequest, response: FetchErrorResponse, hint?: string);
 }
+/**
+ * undici fails a timed-out request with a bare `fetch failed` or `terminated`
+ * and keeps the timeout only in the error's `cause` chain.
+ */
+export declare function isFetchTimeoutError(error: unknown): boolean;
+export declare class FetchTimeoutError extends PnpmError {
+    constructor(code: string, url: string, timeout: number | undefined, opts: {
+        attempts?: number;
+        cause: unknown;
+    });
+}
 export declare function redactUrlCredentials(text: string): string;
 /**
  * Make untrusted, URL-bearing text safe to print or log: redact inline
@@ -57,3 +68,13 @@ export declare function redactAndSanitizeMultiline(text: string): string;
 export declare class LockfileMissingDependencyError extends PnpmError {
     constructor(depPath: string);
 }
+/**
+ * Whether `value` is an `Error`, whichever way the runtime created it.
+ *
+ * `util.types.isNativeError` misses the errors that StackBlitz WebContainers
+ * reject asynchronous `fs` calls with: they inherit from `Error`, but the
+ * native constructor did not create them. `instanceof Error` misses errors
+ * from another realm, such as the ones code under Jest's VM contexts catches.
+ * Either check passing is enough.
+ */
+export declare function isError(value: unknown): value is Error;

package/lib/index.js

@@ -1,3 +1,4 @@
+import util from 'node:util';
 import { WANTED_LOCKFILE } from '@pnpm/constants';
 export class PnpmError extends Error {
     code;
@@ -39,6 +40,34 @@ export class FetchError extends PnpmError {
         this.response = response;
     }
 }
+/**
+ * undici codes for a request that made no progress for `fetchTimeout`: no
+ * response head, or a body that stopped arriving.
+ */
+const FETCH_TIMEOUT_ERROR_CODES = new Set(['UND_ERR_HEADERS_TIMEOUT', 'UND_ERR_BODY_TIMEOUT']);
+/**
+ * undici fails a timed-out request with a bare `fetch failed` or `terminated`
+ * and keeps the timeout only in the error's `cause` chain.
+ */
+export function isFetchTimeoutError(error) {
+    let current = error;
+    for (let depth = 0; depth < 8 && current != null && typeof current === 'object'; depth++) {
+        const { code, cause } = current;
+        if (typeof code === 'string' && FETCH_TIMEOUT_ERROR_CODES.has(code))
+            return true;
+        current = cause;
+    }
+    return false;
+}
+export class FetchTimeoutError extends PnpmError {
+    constructor(code, url, timeout, opts) {
+        const reason = timeout == null ? 'waiting for data' : `no data received for ${timeout}ms`;
+        super(code, `GET ${redactUrlForDisplay(url)}: timed out, ${reason}`, {
+            ...opts,
+            hint: 'The registry stopped responding. If it is just slow, increase the fetchTimeout setting.',
+        });
+    }
+}
 /**
  * Strip `user:pass@` (or `user@`) userinfo that follows a URL scheme in any
  * text, e.g. `GET https://user:pass@host/pkg: …` → `GET https://host/pkg: …`.
@@ -191,4 +220,16 @@ export class LockfileMissingDependencyError extends PnpmError {
         });
     }
 }
+/**
+ * Whether `value` is an `Error`, whichever way the runtime created it.
+ *
+ * `util.types.isNativeError` misses the errors that StackBlitz WebContainers
+ * reject asynchronous `fs` calls with: they inherit from `Error`, but the
+ * native constructor did not create them. `instanceof Error` misses errors
+ * from another realm, such as the ones code under Jest's VM contexts catches.
+ * Either check passing is enough.
+ */
+export function isError(value) {
+    return util.types.isNativeError(value) || value instanceof Error;
+}
 //# sourceMappingURL=index.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pnpm/error",
-  "version": "1100.1.4",
+  "version": "1100.2.1",
   "description": "An error class for pnpm errors",
   "keywords": [
     "pnpm",
@@ -32,7 +32,7 @@
   },
   "devDependencies": {
     "@jest/globals": "30.4.1",
-    "@pnpm/error": "1100.1.4"
+    "@pnpm/error": "1100.2.1"
   },
   "engines": {
     "node": ">=22.13"