isolated-vm - npm Package Compare versions

Comparing version 4.7.2 to 5.0.0

vendor/v8_inspector/nodejs_v22.0.0.h

package.json

		{
		"name": "isolated-vm",
		"version": "4.7.2",
		"version": "5.0.0",
		"description": "Access to multiple isolates",
		@@ -8,3 +8,3 @@ "main": "isolated-vm.js",
		"engines": {
		"node": ">=16.0.0"
		"node": ">=18.0.0"
		},
		@@ -24,3 +24,3 @@ "scripts": {
		"isolated-vm": ".",
		"prebuild": "^12.1.0"
		"prebuild": "^13.0.0"
		},
		@@ -27,0 +27,0 @@ "binary": {

README.md

		@@ -74,3 +74,3 @@ [![npm version](https://badgen.now.sh/npm/v/isolated-vm)](https://www.npmjs.com/package/isolated-vm)
		* Arch Linux users should run: `sudo pacman -S make gcc python`
		* Red Hat users should run: `sudo dnf install python3 gcc gcc-c++ zlib-devel brotli-devel openssl-devel libuv-devel`
		* Red Hat users should run: `sudo dnf install python3 make gcc gcc-c++ zlib-devel brotli-devel openssl-devel`

		@@ -116,8 +116,2 @@

		Against potentially hostile code you should also consider turning on [v8 untrusted code
		mitigations](https://v8.dev/docs/untrusted-code-mitigations), which helps address the class of
		speculative execution attacks known as Spectre and Meltdown. You can enable this feature by running
		`node` with the `--untrusted-code-mitigations` flag. This feature comes with a slight performance
		cost and must be enabled per-process, therefore nodejs disables it by default.

		v8 is a relatively robust runtime, but there are always new and exciting ways to crash, hang,
		@@ -124,0 +118,0 @@ exploit, or otherwise disrupt a process with plain old JavaScript. Your application must be

native-example/README.md

vendor/v8_inspector/nodejs_v16.0.0.h

vendor/v8_inspector/nodejs_v16.11.0.h

src/external_copy/external_copy.cc