Skip to content

chore(sandbox): publish @bunny.net/sandbox to npm #109

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jamie-at-bunny merged 2 commits into from
Jul 1, 2026
Merged

chore(sandbox): publish @bunny.net/sandbox to npm #109

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3a6f526
chore(sandbox): publish @bunny.net/sandbox to npm
jamie-at-bunny Jul 1, 2026
5c07f9f
Update .changeset/publish-sandbox.md
jamie-at-bunny Jul 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/publish-sandbox.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"@bunny.net/sandbox": patch

@greptile-apps greptile-apps Bot Jul 1, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 TypeScript-source exports will fail for Node.js consumers

packages/sandbox/package.json exports ./src/index.ts directly (no build script, no dist/), unlike the already-published sibling @bunny.net/openapi-client which compiles to dist/index.js before publishing. Any Node.js consumer who runs npm install @bunny.net/sandbox will get an unresolvable TypeScript entry point. The README.md only shows bun add, so Bun-only seems intentional — but without an engines field (e.g. "engines": { "bun": ">=1.0.0" }) in package.json, npm gives no signal that Node.js is unsupported and the package will silently fail for non-Bun environments.

Fix in Claude Code

---

Publish @bunny.net/sandbox to npm

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 1, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Add sandbox publishing to the release workflow

When this changeset is versioned and merged, the current release workflow still will not publish @bunny.net/sandbox: I checked .github/workflows/release.yml, and the version job only exposes outputs for cli/database-shell/openapi-client/scriptable-dns-types, with publish jobs only for those packages. Since there is no sandbox version check or publish job, this change will bump the package but leave it unpublished on npm, so the stated release action never happens.

Useful? React with 👍 / 👎.

1 change: 1 addition & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ Monorepo for the [bunny.net](https://bunny.net) CLI and supporting packages.
| ------------------------------------------------------------------------ | ------------------------------------ | ------------------------------------------------------------ |
| [`packages/cli/`](packages/cli/) | `@bunny.net/cli` | Command-line interface for bunny.net |
| [`packages/openapi-client/`](packages/openapi-client/) | `@bunny.net/openapi-client` | Standalone, type-safe OpenAPI client for bunny.net |
| [`packages/sandbox/`](packages/sandbox/) | `@bunny.net/sandbox` | Standalone sandbox SDK over Magic Containers and SSH |
| [`packages/app-config/`](packages/app-config/) | `@bunny.net/app-config` | Shared Zod schemas, types, and JSON Schema for `bunny.jsonc` |
| [`packages/database-shell/`](packages/database-shell/) | `@bunny.net/database-shell` | Standalone interactive SQL shell for libSQL databases |
| [`packages/database-openapi/`](packages/database-openapi/) | `@bunny.net/database-openapi` | Generate OpenAPI 3.0 specs from a database schema |
Expand Down