Skip to content

Enable the wasm interpreter, drumbrake in v8 #61166

Closed as not planned
Closed as not planned
Enable the wasm interpreter, drumbrake in v8#61166
Labels
feature requestIssues requesting new Node.js features.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.wasmIssues and PRs related to WebAssembly.

Description

@yanjiew1
yanjiew1
opened on Dec 24, 2025

What is the problem this feature will solve?

Currently, when Node.js is run with JIT disabled, WebAssembly is unavailable.

What is the feature you are proposing to solve the problem?

I propose enabling the WebAssembly interpreter, Drumbrake, when building V8. When Node is run with JIT disabled, Drumbrake could be used to execute WebAssembly modules.

Supporting WebAssembly in jitless mode would be beneficial because it would allow the built-in fetch() to work when Node is running with --jitless, since undici depends on WebAssembly (see: nodejs/undici#4708).

What alternatives have you considered?

No response

Activity

  1. yanjiew1
    added
    feature requestIssues requesting new Node.js features.
    on Dec 24, 2025
  2. github-project-automation
    added this to Node.js feature requestson Dec 24, 2025
  3. github-project-automation
    moved this to Awaiting Triage in Node.js feature requestson Dec 24, 2025

  4. targos commented on Dec 24, 2025

    @targos
    targos
    on Dec 24, 2025
    Member

    Is it enabled by default in pure V8 or Chromium ?

  5. targos commented on Dec 26, 2025

    @targos
    targos
    on Dec 26, 2025
    Member

    It's not: https://github.com/v8/v8/blob/4201bfaacc594cf609c91ce721f44ffaa0f37653/gni/v8.gni#L99-L100

  6. VoltrexKeyva
    added
    wasmIssues and PRs related to WebAssembly.
    on Dec 30, 2025

  7. Renegade334 commented on Feb 15, 2026

    @Renegade334
    Renegade334
    on Feb 15, 2026
    Member

    Drumbrake has both platform and architecture restrictions that don't cover our official builds, and also mandates enabling pointer compression, so I don't see any way in which it gets enabled by default in the build environment. However, it could be worth adding a configure option for custom builds.

  8. github-actions commented on Jul 20, 2026

    @github-actions
    github-actionsbot
    on Jul 20, 2026 – with GitHub Actions
    Contributor

    This issue has been marked as stale due to 90 days of inactivity.
    It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.

  9. github-actions
    added
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Jul 20, 2026

  10. github-actions commented on Aug 20, 2026

    @github-actions
    github-actionsbot
    on Aug 20, 2026 – with GitHub Actions
    Contributor

    This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
    If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.

  11. github-actions
    closed this as not plannedon Aug 20, 2026

  12. Renegade334 commented on Oct 2, 2026

    @Renegade334
    Renegade334
    on Oct 2, 2026
    Member

    Obviated by #66459.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature requestIssues requesting new Node.js features.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.wasmIssues and PRs related to WebAssembly.

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions