@types/node
Advanced tools
| { | ||
| "name": "@types/node", | ||
| "version": "25.0.10", | ||
| "version": "25.1.0", | ||
| "description": "TypeScript definitions for node", | ||
@@ -153,4 +153,4 @@ "homepage": "https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node", | ||
| "peerDependencies": {}, | ||
| "typesPublisherContentHash": "d49085cfe2d18bc2a8f6602d8afed8d606b5972e07f6c51d09eb4d72dbe89bbc", | ||
| "typesPublisherContentHash": "44178b0b7abfa729c2d925a0f2868f64a6c34ff28a1c4e3ea939c65fe2ea10d4", | ||
| "typeScriptVersion": "5.2" | ||
| } |
+1
-1
@@ -11,3 +11,3 @@ # Installation | ||
| ### Additional Details | ||
| * Last updated: Wed, 21 Jan 2026 23:30:02 GMT | ||
| * Last updated: Wed, 28 Jan 2026 16:44:06 GMT | ||
| * Dependencies: [undici-types](https://npmjs.com/package/undici-types) | ||
@@ -14,0 +14,0 @@ |
+16
-0
@@ -126,2 +126,10 @@ /** | ||
| allowUnknownNamedParameters?: boolean | undefined; | ||
| /** | ||
| * If `true`, enables the defensive flag. When the defensive flag is enabled, | ||
| * language features that allow ordinary SQL to deliberately corrupt the database file are disabled. | ||
| * The defensive flag can also be set using `enableDefensive()`. | ||
| * @since v25.1.0 | ||
| * @default false | ||
| */ | ||
| defensive?: boolean | undefined; | ||
| } | ||
@@ -299,2 +307,10 @@ interface CreateSessionOptions { | ||
| /** | ||
| * Enables or disables the defensive flag. When the defensive flag is active, | ||
| * language features that allow ordinary SQL to deliberately corrupt the database file are disabled. | ||
| * See [`SQLITE_DBCONFIG_DEFENSIVE`](https://www.sqlite.org/c3ref/c_dbconfig_defensive.html#sqlitedbconfigdefensive) in the SQLite documentation for details. | ||
| * @since v25.1.0 | ||
| * @param active Whether to set the defensive flag. | ||
| */ | ||
| enableDefensive(active: boolean): void; | ||
| /** | ||
| * This method is a wrapper around [`sqlite3_db_filename()`](https://sqlite.org/c3ref/db_filename.html) | ||
@@ -301,0 +317,0 @@ * @since v24.0.0 |
+39
-11
@@ -752,3 +752,3 @@ /** | ||
| * `, { context: referencingModule.context }); | ||
| * moduleMap.set(specifier, linkedModule); | ||
| * moduleMap.set(specifier, requestedModule); | ||
| * // Resolve the dependencies of the new module as well. | ||
@@ -823,15 +823,43 @@ * resolveAndLinkDependencies(requestedModule); | ||
| /** | ||
| * Evaluate the module. | ||
| * 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. | ||
| * | ||
| * This must be called after the module has been linked; otherwise it will reject. | ||
| * It could be called also when the module has already been evaluated, in which | ||
| * case it will either do nothing if the initial evaluation ended in success | ||
| * (`module.status` is `'evaluated'`) or it will re-throw the exception that the | ||
| * initial evaluation resulted in (`module.status` is `'errored'`). | ||
| * If the module is a `vm.SourceTextModule`, `evaluate()` must be called after the module has been instantiated; | ||
| * otherwise `evaluate()` will return a rejected promise. | ||
| * | ||
| * This method cannot be called while the module is being evaluated | ||
| * (`module.status` is `'evaluating'`). | ||
| * For a `vm.SourceTextModule`, the promise returned by `evaluate()` may be fulfilled either | ||
| * synchronously or asynchronously: | ||
| * | ||
| * 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. | ||
| * 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. | ||
@@ -838,0 +866,0 @@ */ |
Sorry, the diff of this file is too big to display
Network access
Supply chain riskThis module accesses the network.
Found 1 instance in 1 package
Uses eval
Supply chain riskPackage uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.
Found 1 instance in 1 package
Debug access
Supply chain riskUses debug, reflection and dynamic code execution features.
Found 2 instances in 1 package
Dynamic require
Supply chain riskDynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.
Found 1 instance in 1 package
Environment variable access
Supply chain riskPackage accesses environment variables, which may be a sign of credential stuffing or data theft.
Found 7 instances in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 1 instance in 1 package
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
Found 1 instance in 1 package
Network access
Supply chain riskThis module accesses the network.
Found 1 instance in 1 package
Uses eval
Supply chain riskPackage uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.
Found 1 instance in 1 package
Debug access
Supply chain riskUses debug, reflection and dynamic code execution features.
Found 2 instances in 1 package
Dynamic require
Supply chain riskDynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.
Found 1 instance in 1 package
Environment variable access
Supply chain riskPackage accesses environment variables, which may be a sign of credential stuffing or data theft.
Found 7 instances in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 1 instance in 1 package
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
Found 1 instance in 1 package
2371249
0.16%52930
0.1%