48e9249270
Follow-up to #1613, which fixed the `glob@11` deprecation warning in `e2b` but left `@e2b/cli` warning via `@npmcli/package-json@5 → glob@10`. That PR proposed `@npmcli/package-json@7`, but `^7` alone isn't enough — 7.0.0–7.0.2 still depend on the equally deprecated `glob@^11`, and the move to `glob@13` only landed in **7.0.4**, so this pins `^7.0.5`. Since `@npmcli/package-json@7` requires Node `^20.17.0 || >=22.9.0`, the CLI's Node 22 floor moves from `>=22` to `>=22.9.0` — matching the dependency exactly rather than excluding anyone it still supports. Node 20 support is unchanged, since `^20.17.0` covers the existing `>=20.18.1 <21`. ## Before / after ```console $ npm install @e2b/cli # before npm warn deprecated glob@11.1.0: Old versions of glob are not supported... npm warn deprecated glob@10.5.0: Old versions of glob are not supported... added 183 packages in 4s $ npm install @e2b/cli # after (both tarballs packed locally) added 145 packages in 1s ``` No API change. `e2b template init` is the only consumer, and the `PackageJson.load`/`create`/`update`/`save` surface it uses is unchanged across the bump. ## Verification - Packed `e2b` + `@e2b/cli` and installed into a scratch project with `overrides` pointing `e2b` at the local tarball (the post-release state): zero deprecation warnings, `npm ls glob --all` reports only `glob@13.0.6`. - Ran `e2b template init -n my-tmpl -l typescript` from that packed install against a real host `package.json` — scripts added, pre-existing scripts preserved. - `packages/cli` suite: 102 passed / 1 skipped, including all 14 `template init` tests, which assert on the written `package.json` in both the `load` (existing file) and `create` (no file) branches. `template/create.test.ts` fails identically on a clean tree in this environment — it requires `E2B_API_KEY`. - `pnpm run format` / `lint` / `typecheck` clean. `@types/npmcli__package-json` stays at `^4.0.4`; v7 ships no types. - `.tool-versions` is untouched: the pinned `nodejs 22.18.0` already satisfies `>=22.9.0`, so CI (which derives `node-version` from that file) needs no change. Closes SDK-297. Follow-up to #1613 (SDK-296). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude <noreply@anthropic.com>
E2B CLI
This CLI tool allows you to build manager your running E2B sandbox and sandbox templates. Learn more in our documentation.
1. Install the CLI
Using Homebrew (on macOS)
brew install e2b
Using NPM
npm install -g @e2b/cli
2. Authenticate
e2b auth login
Note
To authenticate without the ability to open the browser, provide
E2B_ACCESS_TOKENas an environment variable. You can find your token in Account Settings under the Team selector at e2b.dev/dashboard. Then use the CLI like this:E2B_ACCESS_TOKEN=sk_e2b_... e2b template create.
Important
Note the distinction between
E2B_ACCESS_TOKENandE2B_API_KEY.
3. Check out docs
Visit our CLI documentation to learn more.
