Skip to content

Title: npm install @computeragent/runtime-e2b, @computeragent/runtime-vzvm, returns 404 — package not published #30

Description

@harshit-lyzr

What happened

Short summary I tried to install @computeragent/runtime-e2b (and similarly @computeragent/runtime-bwrap / @computeragent/runtime-vzvm) with npm but got a 404 (package not found). The package exists in the monorepo at packages/runtime-e2b, but it appears not to be published to the public npm registry, so npm install fails.

What you expected

Either the package should be published to npm (so npm install works), or the README/docs should clearly state that these are workspace-only packages and document how to install/build them locally (e.g., clone repo + pnpm install && pnpm -w build + npm pack / local install, or instructions for npm link), or publish them to a registry (npm or GitHub Packages) and update docs with the registry URL.

Environment

macOS

Logs / stack trace

Quick checks

  • I've run pnpm -r build and pnpm -r test from the latest main
  • My environment matches the README's prereqs (Node ≥ 20, pnpm ≥ 9)

Activity

  1. Chinmay-10 commented on Sep 17, 2026

    @Chinmay-10

    Hi! I reproduced this issue locally today — both @computeragent/runtime-e2b and @computeragent/runtime-vzvm currently return 404 from the npm registry.

    I’d like to work on this issue if it’s still available. Would you be okay assigning it to me? I can investigate the package publishing/configuration and submit a PR with the necessary fix and tests/documentation.

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

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions