E2B SDK v2.30.0 adds network mount watching and fixes four bugs

`e2b@2.30.0` ships one minor change and four patch fixes. The minor addition is an `allowNetworkMounts`/`allow_network_mounts` flag for filesystem directory watching. Because events on network filesystem mounts (NFS, CIFS, SMB, FUSE) can be unreliable or silently dropped, such paths are rejected by default; enabling this option opts into watching them. The feature requires `envd 0.6.4` or later — using it against an older sandbox raises a template error.

First, `Sandbox.getMetrics()` was incorrectly sending `start` and `end` as path parameters instead of query parameters, causing the requested time range to be silently ignored.

The four patch fixes address distinct bugs. First, `Sandbox.getMetrics()` was incorrectly sending `start` and `end` as path parameters instead of query parameters, causing the requested time range to be silently ignored. Second, `Volume.readFile` was returning `undefined` instead of an empty `Blob` or `ReadableStream` for empty files, and the documented 60-second default request timeout is now also applied to volume content requests. Third, the `Sandbox.kill()` instance method now returns a `boolean` — `true` if the sandbox was killed, `false` if it was not found — bringing it in line with the static `Sandbox.kill()` and the Python SDK. Fourth, non-2xx API and `envd` responses with empty bodies (e.g. `Content-Length: 0`) now raise an error rather than being silently treated as successful.

Key facts

1. 01New `allowNetworkMounts`/`allow_network_mounts` option enables watching paths on NFS, CIFS, SMB, and FUSE mounts, which are rejected by default.
2. 02Network mount watching requires `envd 0.6.4` or later; using it with an older sandbox raises a template error.
3. 03`Sandbox.getMetrics()` fix: `start` and `end` were sent as path parameters instead of query parameters, silently ignoring the requested time range.
4. 04`Volume.readFile` fix: now returns an empty `Blob`/`ReadableStream` for empty files instead of `undefined`; 60s default timeout now applied to volume content requests.
5. 05`Sandbox.kill()` instance method now returns `boolean` (`true` = killed, `false` = not found), matching the static method and Python SDK.
6. 06Non-2xx responses with empty bodies (e.g. `Content-Length: 0`) now raise an error instead of being treated as successful.

Topics