@openclaw/feishu 2026.7.2-beta.4 → 2026.7.2-beta.7

package/node_modules/@types/node/vm.d.ts

@@ -1,1136 +0,0 @@
-declare module "node:vm" {
-    import { NonSharedBuffer } from "node:buffer";
-    import { ImportAttributes, ImportPhase } from "node:module";
-    interface Context extends NodeJS.Dict<any> {}
-    interface BaseOptions {
-        /**
-         * Specifies the filename used in stack traces produced by this script.
-         * @default ''
-         */
-        filename?: string | undefined;
-        /**
-         * Specifies the line number offset that is displayed in stack traces produced by this script.
-         * @default 0
-         */
-        lineOffset?: number | undefined;
-        /**
-         * Specifies the column number offset that is displayed in stack traces produced by this script.
-         * @default 0
-         */
-        columnOffset?: number | undefined;
-    }
-    type DynamicModuleLoader<T> = (
-        specifier: string,
-        referrer: T,
-        importAttributes: ImportAttributes,
-        phase: ImportPhase,
-    ) => Module | Promise<Module>;
-    interface ScriptOptions extends BaseOptions {
-        /**
-         * Provides an optional data with V8's code cache data for the supplied source.
-         */
-        cachedData?: NodeJS.ArrayBufferView | undefined;
-        /** @deprecated in favor of `script.createCachedData()` */
-        produceCachedData?: boolean | undefined;
-        /**
-         * Used to specify how the modules should be loaded during the evaluation of this script when `import()` is called. This option is
-         * part of the experimental modules API. We do not recommend using it in a production environment. For detailed information, see
-         * [Support of dynamic `import()` in compilation APIs](https://nodejs.org/docs/latest-v26.x/api/vm.html#support-of-dynamic-import-in-compilation-apis).
-         * @experimental
-         */
-        importModuleDynamically?:
-            | DynamicModuleLoader<Script>
-            | typeof constants.USE_MAIN_CONTEXT_DEFAULT_LOADER
-            | undefined;
-    }
-    interface RunningScriptOptions extends BaseOptions {
-        /**
-         * When `true`, if an `Error` occurs while compiling the `code`, the line of code causing the error is attached to the stack trace.
-         * @default true
-         */
-        displayErrors?: boolean | undefined;
-        /**
-         * Specifies the number of milliseconds to execute code before terminating execution.
-         * If execution is terminated, an `Error` will be thrown. This value must be a strictly positive integer.
-         */
-        timeout?: number | undefined;
-        /**
-         * If `true`, the execution will be terminated when `SIGINT` (Ctrl+C) is received.
-         * Existing handlers for the event that have been attached via `process.on('SIGINT')` will be disabled during script execution, but will continue to work after that.
-         * If execution is terminated, an `Error` will be thrown.
-         * @default false
-         */
-        breakOnSigint?: boolean | undefined;
-    }
-    interface RunningScriptInNewContextOptions
-        extends RunningScriptOptions, Pick<CreateContextOptions, "microtaskMode">
-    {
-        /**
-         * Human-readable name of the newly created context.
-         */
-        contextName?: CreateContextOptions["name"] | undefined;
-        /**
-         * Origin corresponding to the newly created context for display purposes. The origin should be formatted like a URL,
-         * but with only the scheme, host, and port (if necessary), like the value of the `url.origin` property of a `URL` object.
-         * Most notably, this string should omit the trailing slash, as that denotes a path.
-         */
-        contextOrigin?: CreateContextOptions["origin"] | undefined;
-        contextCodeGeneration?: CreateContextOptions["codeGeneration"] | undefined;
-    }
-    interface RunningCodeOptions extends RunningScriptOptions, Pick<ScriptOptions, "cachedData"> {
-        /**
-         * Used to specify how the modules should be loaded during the evaluation of this script when `import()` is called. This option is
-         * part of the experimental modules API. We do not recommend using it in a production environment. For detailed information, see
-         * [Support of dynamic `import()` in compilation APIs](https://nodejs.org/docs/latest-v26.x/api/vm.html#support-of-dynamic-import-in-compilation-apis).
-         * @experimental
-         */
-        importModuleDynamically?:
-            | DynamicModuleLoader<Script>
-            | typeof constants.USE_MAIN_CONTEXT_DEFAULT_LOADER
-            | undefined;
-    }
-    interface RunningCodeInNewContextOptions
-        extends RunningScriptInNewContextOptions, Pick<ScriptOptions, "cachedData">
-    {
-        /**
-         * Used to specify how the modules should be loaded during the evaluation of this script when `import()` is called. This option is
-         * part of the experimental modules API. We do not recommend using it in a production environment. For detailed information, see
-         * [Support of dynamic `import()` in compilation APIs](https://nodejs.org/docs/latest-v26.x/api/vm.html#support-of-dynamic-import-in-compilation-apis).
-         * @experimental
-         */
-        importModuleDynamically?:
-            | DynamicModuleLoader<Script>
-            | typeof constants.USE_MAIN_CONTEXT_DEFAULT_LOADER
-            | undefined;
-    }
-    interface CompileFunctionOptions extends BaseOptions, Pick<ScriptOptions, "cachedData" | "produceCachedData"> {
-        /**
-         * The sandbox/context in which the said function should be compiled in.
-         */
-        parsingContext?: Context | undefined;
-        /**
-         * An array containing a collection of context extensions (objects wrapping the current scope) to be applied while compiling
-         */
-        contextExtensions?: Object[] | undefined;
-        /**
-         * Used to specify how the modules should be loaded during the evaluation of this script when `import()` is called. This option is
-         * part of the experimental modules API. We do not recommend using it in a production environment. For detailed information, see
-         * [Support of dynamic `import()` in compilation APIs](https://nodejs.org/docs/latest-v26.x/api/vm.html#support-of-dynamic-import-in-compilation-apis).
-         * @experimental
-         */
-        importModuleDynamically?:
-            | DynamicModuleLoader<ReturnType<typeof compileFunction>>
-            | typeof constants.USE_MAIN_CONTEXT_DEFAULT_LOADER
-            | undefined;
-    }
-    interface CreateContextOptions {
-        /**
-         * Human-readable name of the newly created context.
-         * @default 'VM Context i' Where i is an ascending numerical index of the created context.
-         */
-        name?: string | undefined;
-        /**
-         * Corresponds to the newly created context for display purposes.
-         * The origin should be formatted like a `URL`, but with only the scheme, host, and port (if necessary),
-         * like the value of the `url.origin` property of a URL object.
-         * Most notably, this string should omit the trailing slash, as that denotes a path.
-         * @default ''
-         */
-        origin?: string | undefined;
-        codeGeneration?:
-            | {
-                /**
-                 * If set to false any calls to eval or function constructors (Function, GeneratorFunction, etc)
-                 * will throw an EvalError.
-                 * @default true
-                 */
-                strings?: boolean | undefined;
-                /**
-                 * If set to false any attempt to compile a WebAssembly module will throw a WebAssembly.CompileError.
-                 * @default true
-                 */
-                wasm?: boolean | undefined;
-            }
-            | undefined;
-        /**
-         * If set to `afterEvaluate`, microtasks will be run immediately after the script has run.
-         */
-        microtaskMode?: "afterEvaluate" | undefined;
-        /**
-         * Used to specify how the modules should be loaded during the evaluation of this script when `import()` is called. This option is
-         * part of the experimental modules API. We do not recommend using it in a production environment. For detailed information, see
-         * [Support of dynamic `import()` in compilation APIs](https://nodejs.org/docs/latest-v26.x/api/vm.html#support-of-dynamic-import-in-compilation-apis).
-         * @experimental
-         */
-        importModuleDynamically?:
-            | DynamicModuleLoader<Context>
-            | typeof constants.USE_MAIN_CONTEXT_DEFAULT_LOADER
-            | undefined;
-    }
-    type MeasureMemoryMode = "summary" | "detailed";
-    interface MeasureMemoryOptions {
-        /**
-         * @default 'summary'
-         */
-        mode?: MeasureMemoryMode | undefined;
-        /**
-         * @default 'default'
-         */
-        execution?: "default" | "eager" | undefined;
-    }
-    interface MemoryMeasurement {
-        total: {
-            jsMemoryEstimate: number;
-            jsMemoryRange: [number, number];
-        };
-    }
-    /**
-     * Instances of the `vm.Script` class contain precompiled scripts that can be
-     * executed in specific contexts.
-     * @since v0.3.1
-     */
-    class Script {
-        constructor(code: string, options?: ScriptOptions | string);
-        /**
-         * Runs the compiled code contained by the `vm.Script` object within the given `contextifiedObject` and returns the result. Running code does not have access
-         * to local scope.
-         *
-         * The following example compiles code that increments a global variable, sets
-         * the value of another global variable, then execute the code multiple times.
-         * The globals are contained in the `context` object.
-         *
-         * ```js
-         * import { createContext, Script } from 'node:vm';
-         *
-         * const context = {
-         *   animal: 'cat',
-         *   count: 2,
-         * };
-         *
-         * const script = new Script('count += 1; name = "kitty";');
-         *
-         * createContext(context);
-         * for (let i = 0; i < 10; ++i) {
-         *   script.runInContext(context);
-         * }
-         *
-         * console.log(context);
-         * // Prints: { animal: 'cat', count: 12, name: 'kitty' }
-         * ```
-         *
-         * Using the `timeout` or `breakOnSigint` options will result in new event loops
-         * and corresponding threads being started, which have a non-zero performance
-         * overhead.
-         * @since v0.3.1
-         * @param contextifiedObject A `contextified` object as returned by the `vm.createContext()` method.
-         * @return the result of the very last statement executed in the script.
-         */
-        runInContext(contextifiedObject: Context, options?: RunningScriptOptions): any;
-        /**
-         * This method is a shortcut to `script.runInContext(vm.createContext(options), options)`.
-         * It does several things at once:
-         *
-         * 1. Creates a new context.
-         * 2. If `contextObject` is an object, contextifies it with the new context.
-         *    If `contextObject` is undefined, creates a new object and contextifies it.
-         *    If `contextObject` is `vm.constants.DONT_CONTEXTIFY`, don't contextify anything.
-         * 3. Compiles the code as a `vm.Script`
-         * 4. Runs the compiled code within the created context. The code does not have access to the scope in
-         *    which this method is called.
-         * 5. Returns the result.
-         *
-         * The following example compiles code that sets a global variable, then executes
-         * the code multiple times in different contexts. The globals are set on and
-         * contained within each individual `context`.
-         *
-         * ```js
-         * import { constants, Script } from 'node:vm';
-         *
-         * const script = new Script('globalVar = "set"');
-         *
-         * const contexts = [{}, {}, {}];
-         * contexts.forEach((context) => {
-         *   script.runInNewContext(context);
-         * });
-         *
-         * console.log(contexts);
-         * // Prints: [{ globalVar: 'set' }, { globalVar: 'set' }, { globalVar: 'set' }]
-         *
-         * // This would throw if the context is created from a contextified object.
-         * // constants.DONT_CONTEXTIFY allows creating contexts with ordinary
-         * // global objects that can be frozen.
-         * const freezeScript = new Script('Object.freeze(globalThis); globalThis;');
-         * const frozenContext = freezeScript.runInNewContext(constants.DONT_CONTEXTIFY);
-         * ```
-         * @since v0.3.1
-         * @param contextObject Either `vm.constants.DONT_CONTEXTIFY` or an object that will be contextified.
-         * If `undefined`, an empty contextified object will be created for backwards compatibility.
-         * @return the result of the very last statement executed in the script.
-         */
-        runInNewContext(
-            contextObject?: Context | typeof constants.DONT_CONTEXTIFY,
-            options?: RunningScriptInNewContextOptions,
-        ): any;
-        /**
-         * Runs the compiled code contained by the `vm.Script` within the context of the
-         * current `global` object. Running code does not have access to local scope, but _does_ have access to the current `global` object.
-         *
-         * The following example compiles code that increments a `global` variable then
-         * executes that code multiple times:
-         *
-         * ```js
-         * import { Script } from 'node:vm';
-         *
-         * global.globalVar = 0;
-         *
-         * const script = new Script('globalVar += 1', { filename: 'myfile.vm' });
-         *
-         * for (let i = 0; i < 1000; ++i) {
-         *   script.runInThisContext();
-         * }
-         *
-         * console.log(globalVar);
-         *
-         * // 1000
-         * ```
-         * @since v0.3.1
-         * @return the result of the very last statement executed in the script.
-         */
-        runInThisContext(options?: RunningScriptOptions): any;
-        /**
-         * Creates a code cache that can be used with the `Script` constructor's `cachedData` option. Returns a `Buffer`. This method may be called at any
-         * time and any number of times.
-         *
-         * The code cache of the `Script` doesn't contain any JavaScript observable
-         * states. The code cache is safe to be saved along side the script source and
-         * used to construct new `Script` instances multiple times.
-         *
-         * Functions in the `Script` source can be marked as lazily compiled and they are
-         * not compiled at construction of the `Script`. These functions are going to be
-         * compiled when they are invoked the first time. The code cache serializes the
-         * metadata that V8 currently knows about the `Script` that it can use to speed up
-         * future compilations.
-         *
-         * ```js
-         * const script = new vm.Script(`
-         * function add(a, b) {
-         *   return a + b;
-         * }
-         *
-         * const x = add(1, 2);
-         * `);
-         *
-         * const cacheWithoutAdd = script.createCachedData();
-         * // In `cacheWithoutAdd` the function `add()` is marked for full compilation
-         * // upon invocation.
-         *
-         * script.runInThisContext();
-         *
-         * const cacheWithAdd = script.createCachedData();
-         * // `cacheWithAdd` contains fully compiled function `add()`.
-         * ```
-         * @since v10.6.0
-         */
-        createCachedData(): NonSharedBuffer;
-        /** @deprecated in favor of `script.createCachedData()` */
-        cachedDataProduced?: boolean;
-        /**
-         * When `cachedData` is supplied to create the `vm.Script`, this value will be set
-         * to either `true` or `false` depending on acceptance of the data by V8.
-         * Otherwise the value is `undefined`.
-         * @since v5.7.0
-         */
-        cachedDataRejected?: boolean;
-        cachedData?: NonSharedBuffer;
-        /**
-         * When the script is compiled from a source that contains a source map magic
-         * comment, this property will be set to the URL of the source map.
-         *
-         * ```js
-         * import vm from 'node:vm';
-         *
-         * const script = new vm.Script(`
-         * function myFunc() {}
-         * //# sourceMappingURL=sourcemap.json
-         * `);
-         *
-         * console.log(script.sourceMapURL);
-         * // Prints: sourcemap.json
-         * ```
-         * @since v19.1.0, v18.13.0
-         */
-        sourceMapURL: string | undefined;
-    }
-    /**
-     * If the given `contextObject` is an object, the `vm.createContext()` method will
-     * [prepare that object](https://nodejs.org/docs/latest-v26.x/api/vm.html#what-does-it-mean-to-contextify-an-object)
-     * and return a reference to it so that it can be used in calls to {@link runInContext} or
-     * [`script.runInContext()`](https://nodejs.org/docs/latest-v26.x/api/vm.html#scriptrunincontextcontextifiedobject-options).
-     * Inside such scripts, the global object will be wrapped by the `contextObject`, retaining all of its
-     * existing properties but also having the built-in objects and functions any standard
-     * [global object](https://es5.github.io/#x15.1) has. Outside of scripts run by the vm module, global
-     * variables will remain unchanged.
-     *
-     * ```js
-     * import { createContext, runInContext } from 'node:vm';
-     *
-     * global.globalVar = 3;
-     *
-     * const context = { globalVar: 1 };
-     * createContext(context);
-     *
-     * runInContext('globalVar *= 2;', context);
-     *
-     * console.log(context);
-     * // Prints: { globalVar: 2 }
-     *
-     * console.log(global.globalVar);
-     * // Prints: 3
-     * ```
-     *
-     * If `contextObject` is omitted (or passed explicitly as `undefined`), a new,
-     * empty contextified object will be returned.
-     *
-     * When the global object in the newly created context is contextified, it has some quirks
-     * compared to ordinary global objects. For example, it cannot be frozen. To create a context
-     * without the contextifying quirks, pass `vm.constants.DONT_CONTEXTIFY` as the `contextObject`
-     * argument. See the documentation of `vm.constants.DONT_CONTEXTIFY` for details.
-     *
-     * The `vm.createContext()` method is primarily useful for creating a single
-     * context that can be used to run multiple scripts. For instance, if emulating a
-     * web browser, the method can be used to create a single context representing a
-     * window's global object, then run all `<script>` tags together within that
-     * context.
-     *
-     * The provided `name` and `origin` of the context are made visible through the
-     * Inspector API.
-     * @since v0.3.1
-     * @param contextObject Either `vm.constants.DONT_CONTEXTIFY` or an object that will be contextified.
-     * If `undefined`, an empty contextified object will be created for backwards compatibility.
-     * @return contextified object.
-     */
-    function createContext(
-        contextObject?: Context | typeof constants.DONT_CONTEXTIFY,
-        options?: CreateContextOptions,
-    ): Context;
-    /**
-     * Returns `true` if the given `object` object has been contextified using {@link createContext},
-     * or if it's the global object of a context created using `vm.constants.DONT_CONTEXTIFY`.
-     * @since v0.11.7
-     */
-    function isContext(sandbox: Context): boolean;
-    /**
-     * The `vm.runInContext()` method compiles `code`, runs it within the context of
-     * the `contextifiedObject`, then returns the result. Running code does not have
-     * access to the local scope. The `contextifiedObject` object _must_ have been
-     * previously `contextified` using the {@link createContext} method.
-     *
-     * If `options` is a string, then it specifies the filename.
-     *
-     * The following example compiles and executes different scripts using a single `contextified` object:
-     *
-     * ```js
-     * import { createContext, runInContext } from 'node:vm';
-     *
-     * const contextObject = { globalVar: 1 };
-     * createContext(contextObject);
-     *
-     * for (let i = 0; i < 10; ++i) {
-     *   runInContext('globalVar *= 2;', contextObject);
-     * }
-     * console.log(contextObject);
-     * // Prints: { globalVar: 1024 }
-     * ```
-     * @since v0.3.1
-     * @param code The JavaScript code to compile and run.
-     * @param contextifiedObject The `contextified` object that will be used as the `global` when the `code` is compiled and run.
-     * @return the result of the very last statement executed in the script.
-     */
-    function runInContext(code: string, contextifiedObject: Context, options?: RunningCodeOptions | string): any;
-    /**
-     * This method is a shortcut to
-     * `(new vm.Script(code, options)).runInContext(vm.createContext(options), options)`.
-     * If `options` is a string, then it specifies the filename.
-     *
-     * It does several things at once:
-     *
-     * 1. Creates a new context.
-     * 2. If `contextObject` is an object, contextifies it with the new context.
-     *    If  `contextObject` is undefined, creates a new object and contextifies it.
-     *    If `contextObject` is `vm.constants.DONT_CONTEXTIFY`, don't contextify anything.
-     * 3. Compiles the code as a`vm.Script`
-     * 4. Runs the compield code within the created context. The code does not have access to the scope in
-     *    which this method is called.
-     * 5. Returns the result.
-     *
-     * The following example compiles and executes code that increments a global
-     * variable and sets a new one. These globals are contained in the `contextObject`.
-     *
-     * ```js
-     * import { runInNewContext, constants } from 'node:vm';
-     *
-     * const contextObject = {
-     *   animal: 'cat',
-     *   count: 2,
-     * };
-     *
-     * runInNewContext('count += 1; name = "kitty"', contextObject);
-     * console.log(contextObject);
-     * // Prints: { animal: 'cat', count: 3, name: 'kitty' }
-     *
-     * // This would throw if the context is created from a contextified object.
-     * // vm.constants.DONT_CONTEXTIFY allows creating contexts with ordinary global objects that
-     * // can be frozen.
-     * const frozenContext = runInNewContext(
-     *   'Object.freeze(globalThis); globalThis;',
-     *   constants.DONT_CONTEXTIFY,
-     * );
-     * ```
-     * @since v0.3.1
-     * @param code The JavaScript code to compile and run.
-     * @param contextObject Either `vm.constants.DONT_CONTEXTIFY` or an object that will be contextified.
-     * If `undefined`, an empty contextified object will be created for backwards compatibility.
-     * @return the result of the very last statement executed in the script.
-     */
-    function runInNewContext(
-        code: string,
-        contextObject?: Context | typeof constants.DONT_CONTEXTIFY,
-        options?: RunningCodeInNewContextOptions | string,
-    ): any;
-    /**
-     * `vm.runInThisContext()` compiles `code`, runs it within the context of the
-     * current `global` and returns the result. Running code does not have access to
-     * local scope, but does have access to the current `global` object.
-     *
-     * If `options` is a string, then it specifies the filename.
-     *
-     * The following example illustrates using both `vm.runInThisContext()` and
-     * the JavaScript [`eval()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/eval) function to run the same code:
-     *
-     * ```js
-     * import { runInThisContext } from 'node:vm';
-     * let localVar = 'initial value';
-     *
-     * const vmResult = runInThisContext('localVar = "vm";');
-     * console.log(`vmResult: '${vmResult}', localVar: '${localVar}'`);
-     * // Prints: vmResult: 'vm', localVar: 'initial value'
-     *
-     * const evalResult = eval('localVar = "eval";');
-     * console.log(`evalResult: '${evalResult}', localVar: '${localVar}'`);
-     * // Prints: evalResult: 'eval', localVar: 'eval'
-     * ```
-     *
-     * Because `vm.runInThisContext()` does not have access to the local scope, `localVar` is unchanged. In contrast,
-     * [`eval()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/eval) _does_ have access to the
-     * local scope, so the value `localVar` is changed. In this way `vm.runInThisContext()` is much like an [indirect `eval()` call](https://es5.github.io/#x10.4.2), e.g.`(0,eval)('code')`.
-     * @since v0.3.1
-     * @param code The JavaScript code to compile and run.
-     * @return the result of the very last statement executed in the script.
-     */
-    function runInThisContext(code: string, options?: RunningCodeOptions | string): any;
-    /**
-     * Compiles the given code into the provided context (if no context is
-     * supplied, the current context is used), and returns it wrapped inside a
-     * function with the given `params`.
-     * @since v10.10.0
-     * @param code The body of the function to compile.
-     * @param params An array of strings containing all parameters for the function.
-     */
-    function compileFunction(
-        code: string,
-        params?: readonly string[],
-        options?: CompileFunctionOptions,
-    ): Function & Pick<Script, "cachedData" | "cachedDataProduced" | "cachedDataRejected">;
-    /**
-     * Measure the memory known to V8 and used by all contexts known to the
-     * current V8 isolate, or the main context.
-     *
-     * The format of the object that the returned Promise may resolve with is
-     * specific to the V8 engine and may change from one version of V8 to the next.
-     *
-     * The returned result is different from the statistics returned by `v8.getHeapSpaceStatistics()` in that `vm.measureMemory()` measure the
-     * memory reachable by each V8 specific contexts in the current instance of
-     * the V8 engine, while the result of `v8.getHeapSpaceStatistics()` measure
-     * the memory occupied by each heap space in the current V8 instance.
-     *
-     * ```js
-     * import { createContext, measureMemory } from 'node:vm';
-     * // Measure the memory used by the main context.
-     * measureMemory({ mode: 'summary' })
-     *   // This is the same as vm.measureMemory()
-     *   .then((result) => {
-     *     // The current format is:
-     *     // {
-     *     //   total: { jsMemoryEstimate: 1601828, jsMemoryRange: [1601828, 5275288] },
-     *     //   WebAssembly: { code: 0, metadata: 33962 },
-     *     // }
-     *     console.log(result);
-     *   });
-     *
-     * const context = createContext({ a: 1 });
-     * measureMemory({ mode: 'detailed', execution: 'eager' }).then((result) => {
-     *   // Reference the context here so that it won't be GC'ed
-     *   // until the measurement is complete.
-     *   console.log('Context:', context.a);
-     *   // {
-     *   //   total: { jsMemoryEstimate: 1767100, jsMemoryRange: [1767100, 5440560] },
-     *   //   WebAssembly: { code: 0, metadata: 33962 },
-     *   //   current: { jsMemoryEstimate: 1601828, jsMemoryRange: [1601828, 5275288] },
-     *   //   other: [{ jsMemoryEstimate: 165272, jsMemoryRange: [Array] }],
-     *   // }
-     *   console.log(result);
-     * });
-     * ```
-     * @since v13.10.0
-     * @experimental
-     */
-    function measureMemory(options?: MeasureMemoryOptions): Promise<MemoryMeasurement>;
-    interface ModuleEvaluateOptions extends Pick<RunningScriptOptions, "breakOnSigint" | "timeout"> {}
-    type ModuleLinker = (
-        specifier: string,
-        referencingModule: Module,
-        extra: {
-            attributes: ImportAttributes;
-        },
-    ) => Module | Promise<Module>;
-    type ModuleStatus = "unlinked" | "linking" | "linked" | "evaluating" | "evaluated" | "errored";
-    /**
-     * This feature is only available with the `--experimental-vm-modules` command
-     * flag enabled.
-     *
-     * The `vm.Module` class provides a low-level interface for using
-     * ECMAScript modules in VM contexts. It is the counterpart of the `vm.Script`
-     * class that closely mirrors [Module Record](https://tc39.es/ecma262/#sec-abstract-module-records)s as defined in the ECMAScript
-     * specification.
-     *
-     * Unlike `vm.Script` however, every `vm.Module` object is bound to a context from
-     * its creation.
-     *
-     * Using a `vm.Module` object requires three distinct steps: creation/parsing,
-     * linking, and evaluation. These three steps are illustrated in the following
-     * example.
-     *
-     * This implementation lies at a lower level than the `ECMAScript Module
-     * loader`. There is also no way to interact with the Loader yet, though
-     * support is planned.
-     *
-     * ```js
-     * import vm from 'node:vm';
-     *
-     * const contextifiedObject = vm.createContext({
-     *   secret: 42,
-     *   print: console.log,
-     * });
-     *
-     * // Step 1
-     * //
-     * // Create a Module by constructing a new `vm.SourceTextModule` object. This
-     * // parses the provided source text, throwing a `SyntaxError` if anything goes
-     * // wrong. By default, a Module is created in the top context. But here, we
-     * // specify `contextifiedObject` as the context this Module belongs to.
-     * //
-     * // Here, we attempt to obtain the default export from the module "foo", and
-     * // put it into local binding "secret".
-     *
-     * const rootModule = new vm.SourceTextModule(`
-     *   import s from 'foo';
-     *   s;
-     *   print(s);
-     * `, { context: contextifiedObject });
-     *
-     * // Step 2
-     * //
-     * // "Link" the imported dependencies of this Module to it.
-     * //
-     * // Obtain the requested dependencies of a SourceTextModule by
-     * // `sourceTextModule.moduleRequests` and resolve them.
-     * //
-     * // Even top-level Modules without dependencies must be explicitly linked. The
-     * // array passed to `sourceTextModule.linkRequests(modules)` can be
-     * // empty, however.
-     * //
-     * // Note: This is a contrived example in that the resolveAndLinkDependencies
-     * // creates a new "foo" module every time it is called. In a full-fledged
-     * // module system, a cache would probably be used to avoid duplicated modules.
-     *
-     * const moduleMap = new Map([
-     *   ['root', rootModule],
-     * ]);
-     *
-     * function resolveAndLinkDependencies(module) {
-     *   const requestedModules = module.moduleRequests.map((request) => {
-     *     // In a full-fledged module system, the resolveAndLinkDependencies would
-     *     // resolve the module with the module cache key `[specifier, attributes]`.
-     *     // In this example, we just use the specifier as the key.
-     *     const specifier = request.specifier;
-     *
-     *     let requestedModule = moduleMap.get(specifier);
-     *     if (requestedModule === undefined) {
-     *       requestedModule = new vm.SourceTextModule(`
-     *         // The "secret" variable refers to the global variable we added to
-     *         // "contextifiedObject" when creating the context.
-     *         export default secret;
-     *       `, { context: referencingModule.context });
-     *       moduleMap.set(specifier, requestedModule);
-     *       // Resolve the dependencies of the new module as well.
-     *       resolveAndLinkDependencies(requestedModule);
-     *     }
-     *
-     *     return requestedModule;
-     *   });
-     *
-     *   module.linkRequests(requestedModules);
-     * }
-     *
-     * resolveAndLinkDependencies(rootModule);
-     * rootModule.instantiate();
-     *
-     * // Step 3
-     * //
-     * // Evaluate the Module. The evaluate() method returns a promise which will
-     * // resolve after the module has finished evaluating.
-     *
-     * // Prints 42.
-     * await rootModule.evaluate();
-     * ```
-     * @since v13.0.0, v12.16.0
-     * @experimental
-     */
-    class Module {
-        /**
-         * If the `module.status` is `'errored'`, this property contains the exception
-         * thrown by the module during evaluation. If the status is anything else,
-         * accessing this property will result in a thrown exception.
-         *
-         * The value `undefined` cannot be used for cases where there is not a thrown
-         * exception due to possible ambiguity with `throw undefined;`.
-         *
-         * Corresponds to the `[[EvaluationError]]` field of [Cyclic Module Record](https://tc39.es/ecma262/#sec-cyclic-module-records) s
-         * in the ECMAScript specification.
-         */
-        error: any;
-        /**
-         * The identifier of the current module, as set in the constructor.
-         */
-        identifier: string;
-        context: Context;
-        /**
-         * The namespace object of the module. This is only available after linking
-         * (`module.link()`) has completed.
-         *
-         * Corresponds to the [GetModuleNamespace](https://tc39.es/ecma262/#sec-getmodulenamespace) abstract operation in the ECMAScript
-         * specification.
-         */
-        namespace: Object;
-        /**
-         * The current status of the module. Will be one of:
-         *
-         * * `'unlinked'`: `module.link()` has not yet been called.
-         * * `'linking'`: `module.link()` has been called, but not all Promises returned
-         * by the linker function have been resolved yet.
-         * * `'linked'`: The module has been linked successfully, and all of its
-         * dependencies are linked, but `module.evaluate()` has not yet been called.
-         * * `'evaluating'`: The module is being evaluated through a `module.evaluate()` on
-         * itself or a parent module.
-         * * `'evaluated'`: The module has been successfully evaluated.
-         * * `'errored'`: The module has been evaluated, but an exception was thrown.
-         *
-         * Other than `'errored'`, this status string corresponds to the specification's [Cyclic Module Record](https://tc39.es/ecma262/#sec-cyclic-module-records)'s `[[Status]]` field. `'errored'`
-         * corresponds to `'evaluated'` in the specification, but with `[[EvaluationError]]` set to a
-         * value that is not `undefined`.
-         */
-        status: ModuleStatus;
-        /**
-         * Evaluate the module and its depenendencies. Corresponds to the [Evaluate() concrete method](https://tc39.es/ecma262/#sec-moduleevaluation) field of
-         * [Cyclic Module Record](https://tc39.es/ecma262/#sec-cyclic-module-records)s in the ECMAScript specification.
-         *
-         * If the module is a `vm.SourceTextModule`, `evaluate()` must be called after the module has been instantiated;
-         * otherwise `evaluate()` will return a rejected promise.
-         *
-         * For a `vm.SourceTextModule`, the promise returned by `evaluate()` may be fulfilled either
-         * synchronously or asynchronously:
-         *
-         * 1. If the `vm.SourceTextModule` has no top-level `await` in itself or any of its dependencies, the promise will be
-         *    fulfilled _synchronously_ after the module and all its dependencies have been evaluated.
-         *    1. If the evaluation succeeds, the promise will be _synchronously_ resolved to `undefined`.
-         *    2. If the evaluation results in an exception, the promise will be _synchronously_ rejected with the exception
-         *       that causes the evaluation to fail, which is the same as `module.error`.
-         * 2. If the `vm.SourceTextModule` has top-level `await` in itself or any of its dependencies, the promise will be
-         *    fulfilled _asynchronously_ after the module and all its dependencies have been evaluated.
-         *    1. If the evaluation succeeds, the promise will be _asynchronously_ resolved to `undefined`.
-         *    2. If the evaluation results in an exception, the promise will be _asynchronously_ rejected with the exception
-         *       that causes the evaluation to fail.
-         *
-         * If the module is a `vm.SyntheticModule`, `evaluate()` always returns a promise that fulfills synchronously, see
-         * the specification of [Evaluate() of a Synthetic Module Record](https://tc39.es/ecma262/#sec-smr-Evaluate):
-         *
-         * 1. If the `evaluateCallback` passed to its constructor throws an exception synchronously, `evaluate()` returns
-         *    a promise that will be synchronously rejected with that exception.
-         * 2. If the `evaluateCallback` does not throw an exception, `evaluate()` returns a promise that will be
-         *    synchronously resolved to `undefined`.
-         *
-         * The `evaluateCallback` of a `vm.SyntheticModule` is executed synchronously within the `evaluate()` call, and its
-         * return value is discarded. This means if `evaluateCallback` is an asynchronous function, the promise returned by
-         * `evaluate()` will not reflect its asynchronous behavior, and any rejections from an asynchronous
-         * `evaluateCallback` will be lost.
-         *
-         * `evaluate()` could also be called again after the module has already been evaluated, in which case:
-         *
-         * 1. If the initial evaluation ended in success (`module.status` is `'evaluated'`), it will do nothing
-         *    and return a promise that resolves to `undefined`.
-         * 2. If the initial evaluation resulted in an exception (`module.status` is `'errored'`), it will re-reject
-         *    the exception that the initial evaluation resulted in.
-         *
-         * This method cannot be called while the module is being evaluated (`module.status` is `'evaluating'`).
-         * @return Fulfills with `undefined` upon success.
-         */
-        evaluate(options?: ModuleEvaluateOptions): Promise<void>;
-        /**
-         * Link module dependencies. This method must be called before evaluation, and
-         * can only be called once per module.
-         *
-         * Use `sourceTextModule.linkRequests(modules)` and
-         * `sourceTextModule.instantiate()` to link modules either synchronously or
-         * asynchronously.
-         *
-         * The function is expected to return a `Module` object or a `Promise` that
-         * eventually resolves to a `Module` object. The returned `Module` must satisfy the
-         * following two invariants:
-         *
-         * * It must belong to the same context as the parent `Module`.
-         * * Its `status` must not be `'errored'`.
-         *
-         * If the returned `Module`'s `status` is `'unlinked'`, this method will be
-         * recursively called on the returned `Module` with the same provided `linker` function.
-         *
-         * `link()` returns a `Promise` that will either get resolved when all linking
-         * instances resolve to a valid `Module`, or rejected if the linker function either
-         * throws an exception or returns an invalid `Module`.
-         *
-         * The linker function roughly corresponds to the implementation-defined [HostResolveImportedModule](https://tc39.es/ecma262/#sec-hostresolveimportedmodule) abstract operation in the
-         * ECMAScript
-         * specification, with a few key differences:
-         *
-         * * The linker function is allowed to be asynchronous while [HostResolveImportedModule](https://tc39.es/ecma262/#sec-hostresolveimportedmodule) is synchronous.
-         *
-         * The actual [HostResolveImportedModule](https://tc39.es/ecma262/#sec-hostresolveimportedmodule) implementation used during module
-         * linking is one that returns the modules linked during linking. Since at
-         * that point all modules would have been fully linked already, the [HostResolveImportedModule](https://tc39.es/ecma262/#sec-hostresolveimportedmodule) implementation is fully synchronous per
-         * specification.
-         *
-         * Corresponds to the [Link() concrete method](https://tc39.es/ecma262/#sec-moduledeclarationlinking) field of [Cyclic Module Record](https://tc39.es/ecma262/#sec-cyclic-module-records) s in
-         * the ECMAScript specification.
-         */
-        link(linker: ModuleLinker): Promise<void>;
-    }
-    interface SourceTextModuleOptions extends Pick<ScriptOptions, "cachedData" | "columnOffset" | "lineOffset"> {
-        /**
-         * String used in stack traces.
-         * @default 'vm:module(i)' where i is a context-specific ascending index.
-         */
-        identifier?: string | undefined;
-        context?: Context | undefined;
-        /**
-         * Called during evaluation of this module to initialize the `import.meta`.
-         */
-        initializeImportMeta?: ((meta: ImportMeta, module: SourceTextModule) => void) | undefined;
-        /**
-         * Used to specify how the modules should be loaded during the evaluation of this script when `import()` is called. This option is
-         * part of the experimental modules API. We do not recommend using it in a production environment. For detailed information, see
-         * [Support of dynamic `import()` in compilation APIs](https://nodejs.org/docs/latest-v26.x/api/vm.html#support-of-dynamic-import-in-compilation-apis).
-         * @experimental
-         */
-        importModuleDynamically?: DynamicModuleLoader<SourceTextModule> | undefined;
-    }
-    /**
-     * A `ModuleRequest` represents the request to import a module with given import attributes and phase.
-     * @since 24.4.0
-     */
-    interface ModuleRequest {
-        /**
-         * The specifier of the requested module.
-         */
-        specifier: string;
-        /**
-         * The `"with"` value passed to the `WithClause` in a `ImportDeclaration`, or an empty object if no value was
-         * provided.
-         */
-        attributes: ImportAttributes;
-        /**
-         * The phase of the requested module (`"source"` or `"evaluation"`).
-         */
-        phase: ImportPhase;
-    }
-    /**
-     * This feature is only available with the `--experimental-vm-modules` command
-     * flag enabled.
-     *
-     * The `vm.SourceTextModule` class provides the [Source Text Module Record](https://tc39.es/ecma262/#sec-source-text-module-records) as
-     * defined in the ECMAScript specification.
-     * @since v9.6.0
-     * @experimental
-     */
-    class SourceTextModule extends Module {
-        /**
-         * Creates a new `SourceTextModule` instance.
-         *
-         * Properties assigned to the `import.meta` object that are objects may
-         * allow the module to access information outside the specified `context`. Use
-         * `vm.runInContext()` to create objects in a specific context.
-         *
-         * ```js
-         * import vm from 'node:vm';
-         *
-         * const contextifiedObject = vm.createContext({ secret: 42 });
-         *
-         * const module = new vm.SourceTextModule(
-         *   'Object.getPrototypeOf(import.meta.prop).secret = secret;',
-         *   {
-         *     initializeImportMeta(meta) {
-         *       // Note: this object is created in the top context. As such,
-         *       // Object.getPrototypeOf(import.meta.prop) points to the
-         *       // Object.prototype in the top context rather than that in
-         *       // the contextified object.
-         *       meta.prop = {};
-         *     },
-         *   });
-         * // The module has an empty `moduleRequests` array.
-         * module.linkRequests([]);
-         * module.instantiate();
-         * await module.evaluate();
-         *
-         * // Now, Object.prototype.secret will be equal to 42.
-         * //
-         * // To fix this problem, replace
-         * //     meta.prop = {};
-         * // above with
-         * //     meta.prop = vm.runInContext('{}', contextifiedObject);
-         * ```
-         * @param code JavaScript Module code to parse
-         */
-        constructor(code: string, options?: SourceTextModuleOptions);
-        /**
-         * @deprecated Use `sourceTextModule.moduleRequests` instead.
-         */
-        readonly dependencySpecifiers: readonly string[];
-        /**
-         * Iterates over the dependency graph and returns `true` if any module in its
-         * dependencies or this module itself contains top-level `await` expressions,
-         * otherwise returns `false`.
-         *
-         * The search may be slow if the graph is big enough.
-         *
-         * This requires the module to be instantiated first. If the module is not
-         * instantiated yet, an error will be thrown.
-         * @since v24.9.0
-         */
-        hasAsyncGraph(): boolean;
-        /**
-         * Returns whether the module itself contains any top-level `await` expressions.
-         *
-         * This corresponds to the field `[[HasTLA]]` in [Cyclic Module Record](https://tc39.es/ecma262/#sec-cyclic-module-records) in the
-         * ECMAScript specification.
-         * @since v24.9.0
-         */
-        hasTopLevelAwait(): boolean;
-        /**
-         * Instantiate the module with the linked requested modules.
-         *
-         * This resolves the imported bindings of the module, including re-exported
-         * binding names. When there are any bindings that cannot be resolved,
-         * an error would be thrown synchronously.
-         *
-         * If the requested modules include cyclic dependencies, the
-         * `sourceTextModule.linkRequests(modules)` method must be called on all
-         * modules in the cycle before calling this method.
-         * @since v24.8.0
-         */
-        instantiate(): void;
-        /**
-         * Link module dependencies. This method must be called before evaluation, and
-         * can only be called once per module.
-         *
-         * The order of the module instances in the `modules` array should correspond to the order of
-         * `sourceTextModule.moduleRequests` being resolved. If two module requests have the same
-         * specifier and import attributes, they must be resolved with the same module instance or an
-         * `ERR_MODULE_LINK_MISMATCH` would be thrown. For example, when linking requests for this
-         * module:
-         *
-         * ```js
-         * import foo from 'foo';
-         * import source Foo from 'foo';
-         * ```
-         *
-         * The `modules` array must contain two references to the same instance, because the two
-         * module requests are identical but in two phases.
-         *
-         * If the module has no dependencies, the `modules` array can be empty.
-         *
-         * Users can use `sourceTextModule.moduleRequests` to implement the host-defined
-         * [HostLoadImportedModule](https://tc39.es/ecma262/#sec-HostLoadImportedModule) abstract operation in the ECMAScript specification,
-         * and using `sourceTextModule.linkRequests()` to invoke specification defined
-         * [FinishLoadingImportedModule](https://tc39.es/ecma262/#sec-FinishLoadingImportedModule), on the module with all dependencies in a batch.
-         *
-         * It's up to the creator of the `SourceTextModule` to determine if the resolution
-         * of the dependencies is synchronous or asynchronous.
-         *
-         * After each module in the `modules` array is linked, call
-         * `sourceTextModule.instantiate()`.
-         * @since v24.8.0
-         * @param modules Array of `vm.Module` objects that this module depends on.
-         * The order of the modules in the array is the order of
-         * `sourceTextModule.moduleRequests`.
-         */
-        linkRequests(modules: readonly Module[]): void;
-        /**
-         * The requested import dependencies of this module. The returned array is frozen
-         * to disallow any changes to it.
-         *
-         * For example, given a source text:
-         *
-         * ```js
-         * import foo from 'foo';
-         * import fooAlias from 'foo';
-         * import bar from './bar.js';
-         * import withAttrs from '../with-attrs.ts' with { arbitraryAttr: 'attr-val' };
-         * import source Module from 'wasm-mod.wasm';
-         * ```
-         *
-         * The value of the `sourceTextModule.moduleRequests` will be:
-         *
-         * ```js
-         * [
-         *   {
-         *     specifier: 'foo',
-         *     attributes: {},
-         *     phase: 'evaluation',
-         *   },
-         *   {
-         *     specifier: 'foo',
-         *     attributes: {},
-         *     phase: 'evaluation',
-         *   },
-         *   {
-         *     specifier: './bar.js',
-         *     attributes: {},
-         *     phase: 'evaluation',
-         *   },
-         *   {
-         *     specifier: '../with-attrs.ts',
-         *     attributes: { arbitraryAttr: 'attr-val' },
-         *     phase: 'evaluation',
-         *   },
-         *   {
-         *     specifier: 'wasm-mod.wasm',
-         *     attributes: {},
-         *     phase: 'source',
-         *   },
-         * ];
-         * ```
-         * @since v24.4.0
-         */
-        readonly moduleRequests: readonly ModuleRequest[];
-    }
-    interface SyntheticModuleOptions {
-        /**
-         * String used in stack traces.
-         * @default 'vm:module(i)' where i is a context-specific ascending index.
-         */
-        identifier?: string | undefined;
-        /**
-         * The contextified object as returned by the `vm.createContext()` method, to compile and evaluate this module in.
-         */
-        context?: Context | undefined;
-    }
-    /**
-     * This feature is only available with the `--experimental-vm-modules` command
-     * flag enabled.
-     *
-     * The `vm.SyntheticModule` class provides the [Synthetic Module Record](https://heycam.github.io/webidl/#synthetic-module-records) as
-     * defined in the WebIDL specification. The purpose of synthetic modules is to
-     * provide a generic interface for exposing non-JavaScript sources to ECMAScript
-     * module graphs.
-     *
-     * ```js
-     * import { SyntheticModule } from 'node:vm';
-     *
-     * const source = '{ "a": 1 }';
-     * const syntheticModule = new SyntheticModule(['default'], function() {
-     *   const obj = JSON.parse(source);
-     *   this.setExport('default', obj);
-     * });
-     *
-     * // Use `syntheticModule` in linking
-     * (async () => {
-     *   await syntheticModule.link(() => {});
-     *   await syntheticModule.evaluate();
-     *
-     *   console.log('Default export:', syntheticModule.namespace.default);
-     * })();
-     * ```
-     * @since v13.0.0, v12.16.0
-     * @experimental
-     */
-    class SyntheticModule extends Module {
-        /**
-         * Creates a new `SyntheticModule` instance.
-         * @param exportNames Array of names that will be exported from the module.
-         * @param evaluateCallback Called when the module is evaluated.
-         */
-        constructor(
-            exportNames: string[],
-            evaluateCallback: (this: SyntheticModule) => void,
-            options?: SyntheticModuleOptions,
-        );
-        /**
-         * This method sets the module export binding slots with the given value.
-         *
-         * ```js
-         * import vm from 'node:vm';
-         *
-         * const m = new vm.SyntheticModule(['x'], () => {
-         *   m.setExport('x', 1);
-         * });
-         *
-         * await m.evaluate();
-         *
-         * assert.strictEqual(m.namespace.x, 1);
-         * ```
-         * @since v13.0.0, v12.16.0
-         * @param name Name of the export to set.
-         * @param value The value to set the export to.
-         */
-        setExport(name: string, value: any): void;
-    }
-    /**
-     * Returns an object containing commonly used constants for VM operations.
-     * @since v21.7.0, v20.12.0
-     */
-    namespace constants {
-        /**
-         * A constant that can be used as the `importModuleDynamically` option to `vm.Script`
-         * and `vm.compileFunction()` so that Node.js uses the default ESM loader from the main
-         * context to load the requested module.
-         *
-         * For detailed information, see [Support of dynamic `import()` in compilation APIs](https://nodejs.org/docs/latest-v26.x/api/vm.html#support-of-dynamic-import-in-compilation-apis).
-         * @since v21.7.0, v20.12.0
-         */
-        const USE_MAIN_CONTEXT_DEFAULT_LOADER: number;
-        /**
-         * This constant, when used as the `contextObject` argument in vm APIs, instructs Node.js to create
-         * a context without wrapping its global object with another object in a Node.js-specific manner.
-         * As a result, the `globalThis` value inside the new context would behave more closely to an ordinary
-         * one.
-         *
-         * When `vm.constants.DONT_CONTEXTIFY` is used as the `contextObject` argument to {@link createContext},
-         * the returned object is a proxy-like object to the global object in the newly created context with
-         * fewer Node.js-specific quirks. It is reference equal to the `globalThis` value in the new context,
-         * can be modified from outside the context, and can be used to access built-ins in the new context directly.
-         * @since v22.8.0
-         */
-        const DONT_CONTEXTIFY: number;
-    }
-}
-declare module "vm" {
-    export * from "node:vm";
-}