| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| @e2b_code-interpreter@2.9.1 source code.tar.gz | < 13 hours ago | 2.6 MB | |
| @e2b_code-interpreter@2.9.1 source code.zip | < 13 hours ago | 3.3 MB | |
| README.md | < 13 hours ago | 1.2 kB | |
| Totals: 3 Items | 5.9 MB | 0 | |
Patch Changes
- 8cc9ed1: Document that
logs.stdout,logs.stderrandOutputMessage.linehold raw chunks with newlines kept (join them with''to rebuild the output), and thatResult.png,Result.jpegandResult.pdfare base64-encoded. - 7d10433: Fix
readLinesquadratic line reassembly when streaming long single-line outputs (e.g. base64 images, wide DataFrames, large JSON): decode and scan only each new chunk, accumulating line fragments in an array that is joined once per emitted line, instead of appending to and re-scanning a single string buffer on every chunk. - ac0727b: Fix
OutputMessage.timestampin the JS Code Interpreter to use the backend timestamp (Unix epoch in nanoseconds) sent with each stdout/stderr message, instead of the client clock (new Date().getTime() * 1000). The type is unchanged (number); this aligns the value with the documented contract and the Python SDK. Because nanosecond epoch values exceedNumber.MAX_SAFE_INTEGER, the JS value is precise to a few hundred nanoseconds (documented onOutputMessage.timestamp). - Updated dependencies [320f39d]
- Updated dependencies [36258c1]
- Updated dependencies [8e37561]
- e2b@2.62.1