procxy / ModuleResolutionError

Class: ModuleResolutionError

Defined in: src/shared/errors.ts:137

Thrown when procxy cannot determine the file path of the class's module.

Remarks

Automatic module resolution works by inspecting the call stack and parsing import statements in the caller's source file. It fails in several common scenarios:

• The class is dynamically constructed or passed through several abstraction layers, so the call stack no longer contains a frame in the file that imports the class
• Source files are transpiled to a temp directory that does not match the import path
• The class is defined inline in the same file without an import
• Bundlers inline all modules, making individual file paths unavailable

The fix is always to pass modulePath explicitly:

await procxy(MyClass, new URL('./my-class.js', import.meta.url).pathname);
// or
await procxy(MyClass, { modulePath: './my-class.js' });

Example

import { procxy, ModuleResolutionError } from 'procxy';
import { Worker } from './worker.js';

try {
  const w = await procxy(Worker);
} catch (err) {
  if (err instanceof ModuleResolutionError) {
    console.error(`Could not find module for ${err.className}: ${err.reason}`);
    // Fix: pass an explicit path
  }
}

Extends

• ProcxyError

Constructors

Constructor

new ModuleResolutionError(
   className, 
   reason, 
   context?): ModuleResolutionError;

Defined in: src/shared/errors.ts:138

Parameters

Parameter	Type	Description
className	string	Name of the class whose module path could not be resolved
reason	string	Human-readable explanation of why resolution failed
context?	Record<string, unknown>	-

Returns

ModuleResolutionError

Overrides

ProcxyError.constructor

Properties

Property	Modifier	Type	Description	Inherited from	Defined in
cause?	public	unknown	-	ProcxyError.cause	node_modules/.pnpm/typescript@6.0.2/node_modules/typescript/lib/lib.es2022.error.d.ts:24
className	readonly	string	Name of the class whose module path could not be resolved	-	src/shared/errors.ts:140
context?	readonly	Record<string, unknown>	-	ProcxyError.context	src/shared/errors.ts:45
message	public	string	-	ProcxyError.message	node_modules/.pnpm/typescript@6.0.2/node_modules/typescript/lib/lib.es5.d.ts:1075
name	public	string	-	ProcxyError.name	node_modules/.pnpm/typescript@6.0.2/node_modules/typescript/lib/lib.es5.d.ts:1074
reason	readonly	string	Human-readable explanation of why resolution failed	-	src/shared/errors.ts:142
stack?	public	string	-	ProcxyError.stack	node_modules/.pnpm/typescript@6.0.2/node_modules/typescript/lib/lib.es5.d.ts:1076
stackTraceLimit	static	number	The Error.stackTraceLimit property specifies the number of stack frames collected by a stack trace (whether generated by new Error().stack or Error.captureStackTrace(obj)). The default value is 10 but may be set to any valid JavaScript number. Changes will affect any stack trace captured after the value has been changed. If set to a non-number value, or set to a negative number, stack traces will not capture any frames.	ProcxyError.stackTraceLimit	node_modules/.pnpm/@types+node@25.6.0/node_modules/@types/node/globals.d.ts:67

Methods

captureStackTrace()

static captureStackTrace(targetObject, constructorOpt?): void;

Defined in: node_modules/.pnpm/@types+node@25.6.0/node_modules/@types/node/globals.d.ts:51

Creates a .stack property on targetObject, which when accessed returns a string representing the location in the code at which Error.captureStackTrace() was called.

const myObject = {};
Error.captureStackTrace(myObject);
myObject.stack;  // Similar to `new Error().stack`

The first line of the trace will be prefixed with ${myObject.name}: ${myObject.message}.

The optional constructorOpt argument accepts a function. If given, all frames above constructorOpt, including constructorOpt, will be omitted from the generated stack trace.

The constructorOpt argument is useful for hiding implementation details of error generation from the user. For instance:

function a() {
  b();
}

function b() {
  c();
}

function c() {
  // Create an error without stack trace to avoid calculating the stack trace twice.
  const { stackTraceLimit } = Error;
  Error.stackTraceLimit = 0;
  const error = new Error();
  Error.stackTraceLimit = stackTraceLimit;

  // Capture the stack trace above function b
  Error.captureStackTrace(error, b); // Neither function c, nor b is included in the stack trace
  throw error;
}

a();

Parameters

Parameter	Type
targetObject	object
constructorOpt?	Function

Returns

void

Inherited from

ProcxyError.captureStackTrace

---

prepareStackTrace()

static prepareStackTrace(err, stackTraces): any;

Defined in: node_modules/.pnpm/@types+node@25.6.0/node_modules/@types/node/globals.d.ts:55

Parameters

Parameter	Type
err	Error
stackTraces	CallSite[]

Returns

any

See

https://v8.dev/docs/stack-trace-api#customizing-stack-traces

Inherited from

ProcxyError.prepareStackTrace