npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@vibe-kit/e2b

v0.0.5

Published

E2B sandbox provider for VibeKit.

Readme

@vibe-kit/e2b

E2B sandbox provider for VibeKit.

Installation

npm install @vibe-kit/e2b

Usage

import { VibeKit } from "@vibe-kit/sdk";
import { createE2BProvider } from "@vibe-kit/e2b";

// Create the E2B provider with configuration
const e2bProvider = createE2BProvider({
  apiKey: process.env.E2B_API_KEY!,
  templateId: "vibekit-claude", // optional, will be auto-selected based on agent
});

// Create the VibeKit instance with the provider
const vibeKit = new VibeKit()
  .withAgent({
    type: "claude",
    provider: "anthropic",
    apiKey: process.env.CLAUDE_API_KEY!,
    model: "claude-3-5-sonnet-20241022",
  })
  .withSandbox(e2bProvider) // Pass the provider instance
  .withWorkingDirectory("/var/custom-workdir") // Optional: specify working directory
  .withSecrets({
    // Any environment variables for the sandbox
    NODE_ENV: "development",
  });

// Use the configured instance
const response = await vibeKit.generateCode("Create a simple React component");
console.log(response);

Configuration

The E2B provider accepts the following configuration:

  • apiKey (required): Your E2B API key
  • templateId (optional): E2B template ID. If not provided, it will be auto-selected based on the agent type:
    • claudevibekit-claude
    • opencodevibekit-opencode
    • geminivibekit-gemini
    • codexvibekit-codex

Migration from v0.0.x

Previous versions used a factory pattern with configuration objects. The new version uses provider instances:

Before (v0.0.x)

const vibeKit = new VibeKit()
  .withSandbox({
    type: "e2b",
    apiKey: process.env.E2B_API_KEY!,
    templateId: "vibekit-claude",
  });

After (v0.1.x)

import { createE2BProvider } from "@vibe-kit/e2b";

const e2bProvider = createE2BProvider({
  apiKey: process.env.E2B_API_KEY!,
  templateId: "vibekit-claude",
});

const vibeKit = new VibeKit()
  .withSandbox(e2bProvider);

Features

  • Automatic template selection based on agent type
  • Support for background command execution
  • 1-hour timeout for long-running operations
  • Sandbox pause/resume functionality
  • Port forwarding support
  • Custom working directory support (automatically created with proper permissions)

Requirements

  • Node.js 18+
  • E2B API key

License

MIT