Skip to content

Native engine: support KV, D1, R2, Queues, Workflows, service bindings and assets #116

Open

Description

@sinameraji

docs/native-engine.md lists these as "Not yet. The engine refuses a config that declares them."

A Wrangler project that uses any of them cannot run on the native engine at all, which limits it to Durable Objects-only apps.

Do

  • Decide scope per binding. KV, R2 and Queues are the likely first targets; Workflows and assets are larger.
  • Implement behind the existing shim pattern in packages/cli/src/native/ (workers-shim.js, email-shim.js).
  • Keep the refusal for anything not implemented, so a config never silently half-works.
  • Add conformance cases for each binding that lands.

Done when

The supported bindings are listed in docs/native-engine.md and docs/compatibility.md, with conformance coverage, and unsupported ones still fail loudly.

Activity

  1. added
    m4Milestone M4: multi-node and Teams
    native-engineThe Node-native engine (sobjects dev --engine native)
    on Oct 29, 2026
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

    m4Milestone M4: multi-node and Teamsnative-engineThe Node-native engine (sobjects dev --engine native)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions