Skip to content

Conversation

@Vvkmnn
Copy link

@Vvkmnn Vvkmnn commented Jan 29, 2026

Summary

Updates isolated-vm peer and dev dependencies from ^5.0.1 to ^6.0.0 to support Node.js 24 (current LTS).

Fixes #27

Problem

isolated-vm@5.x uses V8 C++ APIs that changed in Node 24, causing build failures:

npm error unknown type name 'concept'
npm error    22 | concept RequiresStackAllocated =
npm error gyp ERR! build error

Solution

isolated-vm@6.0.0+ was rebuilt with Node 24 support:

  • engines: ">=22.0.0"
  • Published with _nodeVersion: "24.4.0"

Changes

  "peerDependencies": {
-   "isolated-vm": "^5.0.1"
+   "isolated-vm": "^6.0.0"
  },
  "devDependencies": {
-   "isolated-vm": "^5.0.1",
+   "isolated-vm": "^6.0.0",
  }

Note

This bumps the minimum Node version for isolated-vm from 16 to 22. Since @utcp/code-mode already requires node >= 18, this only affects users on Node 18-21 who would need to stay on an older version.


Summary by cubic

Adds Node.js 24 LTS support by fixing isolated-vm build errors caused by V8 API changes.

  • Dependencies

    • Set isolated-vm to ^6.0.0 in peerDependencies and devDependencies.
  • Migration

    • isolated-vm 6 requires Node >=22.
    • If you’re on Node 18–21, stay on the previous release of this package.

Written for commit 4980d9a. Summary will update on new commits.

Copy link

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Node.js 24 incompatibility: isolated-vm peer dependency needs update to ^6.0.0

1 participant