{% /raw %} ## Codesign single-file executables on macOS Previously, the executables produced for macOS by `bun build --compile` could not be code signed, due to an issue with our code handling the Mach-O executable format. Now, these executables can be code signed. {% raw %}In the next version of Bun
— Jarred Sumner (@jarredsumner) February 23, 2025
`bun build` & `Bun․build` gets up to 60% faster on macOS pic.twitter.com/JHA4NceCTo
{% /raw %} Learn how to [codesign compiled executables on macOS](/guides/runtime/codesign-macos-executable). ## Fixed: bun init ↑↓ on Windows The `bun init` command now works properly on Windows with full support for keyboard navigation. Arrow keys (up/down) work correctly for navigating options, Enter works for selection, and Ctrl+C works to cancel the operation. ``` PS C:\Users\bun\project> bun init ? Select a project template - Press return to submit. Blank React ❯ Library ``` Thanks to [@pfgithub](https://github.com/pfgithub) for the contribution! ## Fixed: Regression from v1.2.3 affecting Hono When using Hono with Bun, some applications that `export default` a Hono instance would fail to start with an argument validation error for `routes` in Bun.serve due to a name conflict with the `routes` option in Hono. We've added a workaround and integration tests to avoid introducing regressions that affect Hono in the future. ```js import { Hono } from "hono"; const app = new Hono(); app.get("/", (c) => c.text("Hello World!")); export default app; // Now works properly with Bun.serve ``` ## Node.js compatibility ### Fixed: Stat assertion failure on Windows We fixed a bug that in certain cases caused an assertion failure when calling `stat` in node:fs on Windows. ```js import { stat } from "node:fs/promises"; const stats = await stat("large-file.txt"); console.log(stats.size, stats.mtime); ``` ### Fixed: `net.Socket` error handling A bug has been fixed in `node:net` socket error handling where bare `JSC::Exception` objects could be passed to JavaScript code. `JSC::Exception` is a class used internally by the JavaScript engine, and these objects exhibit strange behavior if they are passed to JavaScript code. Now, all exception objects are properly converted to JavaScript `Error` instances before being passed to error handlers. ```js const socket = new net.Socket(); socket.on("error", (err) => { console.log(err instanceof Error); // Now always true }); ``` Thanks to [@heimskr](https://github.com/heimskr) for fixing this! ### `net.SocketAddress` Bun now exposes the `SocketAddress` class matching Node.js' API, providing a way to represent and manipulate IP socket addresses. ```js import { SocketAddress } from "node:net"; const addr = SocketAddress.parse("[0::1]:1234"); // ipv6 ::1 1234 console.log(addr.family, addr.address, addr.port); ``` Thanks to [@DonIsaac](https://github.com/DonIsaac) for the contribution! ### `Buffer` fixes #### Fixed: `Buffer.prototype.indexOf` for number values with `byteOffset` While improving our Node.js test coverage for `Buffer`, we introduced a bug in Bun v1.2.3 that affected `Buffer.prototype.indexOf` when searching for number values with a byte offset. This has been fixed to properly handle number searches by considering the byte offset, matching Node.js behavior. We've also submitted a PR to Node.js to improve their test coverage for this case (and ours by using their tests). ```js const buffer = Buffer.from("abcdef"); // Searching for character codes (numbers) now works correctly buffer.indexOf(100, 2); // Returns 3 (byte value 100 = 'd' found at index 3) buffer.indexOf(102, 5); // Returns 5 (byte value 102 = 'f' found at index 5) buffer.indexOf(102, -1); // Returns 5 (negative offset searches from the end) buffer.indexOf(102, 6); // Returns -1 (searching past the end of buffer) ``` Thanks to [@nektro](https://github.com/nektro) for the fix! ### Fixed: process.argv in --print and --eval modes The `bun --print` and `bun --eval` commands (or `-p` and `-e`) no longer include `[eval]` in the `process.argv` array. Previously, this was included between the path to the Bun executable and the actual command-line arguments in place of the name of the JavaScript file being run. Now, there is no extra argument in this position which matches Node.js's behavior. ```js // Previously $ bun --print "process.argv" arg1 arg2 ["/path/to/bun", "/your/cwd/[eval]", "arg2"] // Now (matching Node.js) $ bun --print "process.argv" arg1 arg2 ["/path/to/bun", "arg1", "arg2"] ``` Thanks to [@RiskyMH](https://github.com/RiskyMH) for the contribution! ### Fixed: hang when calling `pause()` on `process.stdin` We fixed a bug where stdin streams that were paused immediately would prevent the process from exiting. This affected `readline` and other packages. ```js process.stdin.on("data", () => {}); process.stdin.pause(); // previously: the process would never exit // now: the process exits ``` Thanks to [@pfgithub](https://github.com/pfgithub) for the fix! ## Other improvements ### Fixed: Binary data types in PostgreSQL Bun's PostgreSQL client now correctly handles binary data types and custom type OIDs. This resolves issues with binary format detection and custom data types when using the SQL API. ```js // Binary data and custom types are now properly handled const result = await sql`SELECT bytea_column, custom_type_column FROM my_table`; ``` Thanks to [@cirospaciari](https://github.com/cirospaciari) for the contribution! ### Faster `array.includes` WebKit [rewrote `Array.prototype.includes` in native C++ code](https://github.com/WebKit/WebKit/pull/40613), and this makes `Array.prototype.includes` 1.2 to 2.8 times faster in microbenchmarks. This rewrite allows DFG and FTL (JavaScriptCore's optimizing JIT compilers, which convert JavaScript into native machine code to execute it as fast as possible) to leverage the fast native implementation (similar to `Array.prototype.indexOf`). Thanks to [@sosukesuzuki](https://github.com/sosukesuzuki) for this contribution! ### Dev server stability improvements This release contains several stability improvements for Bun's new development server introduced in 1.2.3. We're excited to keep improving the development experience with Bun in future releases. Thanks to [@paperclover](https://github.com/paperclover) for the fixes! ### `define` support in `bunfig.toml` for static files You can now set the `define` option in the `[serve.static]` section of `bunfig.toml` to inline constants into static files. This works the same way as [the existing runtime option](/docs/runtime/bunfig#define). Unlike environment variables, defines support arbitrary JSON, not just strings. {% codetabs %} ```toml#bunfig.toml [serve.static] # outer quotes for TOML, inner quotes for JavaScript define = { CONFIG = "{ \"version\": \"1.0\", \"beta\": false }" } ``` ```html#index.htmlIn the next version of Bun
— Bun (@bunjavascript) February 25, 2025
Single-file executables on macOS support codesigning, thanks to @joglekar_pranav pic.twitter.com/31VnQ0CME4