{% /raw %} ### Output Source Map URLs in `bun build` To tell browser devtools where to find sourcemaps, tooling inserts a `//# sourceMappingURL=` comment at the end of files. Previously, Bun didn't expose a way to link to external, non-inline sourcemaps via this comment. You can now use `--sourcemap=linked` to tell Bun to insert a `//# sourceMappingURL=` comment at the end of the bundled file, linking to the external sourcemap. ```sh $ bun build src/app.tsx --outdir ./dist --sourcemap=linked --minify ``` This will produce the directory `dist` with `app.js` and `app.js.map`, and the comment `//# sourceMappingURL=app.js.map` to load the sourcemap for debugging. Thanks to [@paperclover](https://github.com/paperclover) for implementing this. ### `console.log` now prints non-indexed properties on arrays Bun now shows prints non-indexed properties on arrays, for example: ```ts#non-indexed-properties.ts const arr = ['a', 'b', 'c']; arr['five'] = 5; console.log(arr); ``` ```sh $ bun non-indexed-properties.ts [ "a", "b", "c", five: 5 ] ``` ### Fixed: WebSocket connection `error` event now includes a `message` When a WebSocket connection fails, the error event now includes a `message` property with a more detailed error message. ```ts const ws = new WebSocket("ws://localhost:8080"); ws.addEventListener("error", (error) => { console.log(error.message); }); // The message previously only was in the "close" event: ws.addEventListener("close", (close) => { console.log(close); }); ``` This prints the following error message: ```ts WebSocket connection to 'ws://localhost:8080/' failed: Failed to connect ``` Instead of only including relevant information in the `close` event, the `error` event on connection failure now includes a `message` property with an error message. ### Fixed: Crash in console.log with WebSocket connection errors When a WebSocket fails to connect, it emits both the `error` and `close` events. ```ts const ws = new WebSocket("ws://localhost:8080"); ws.addEventListener("error", (error) => { // Connection error emitted }); ws.addEventListener("close", () => { // Connection did not fully open, but it is still closed }); ``` Previously, printing `console.log(error)` from a WebSocket connection error would sometimes cause a crash. The code incorrectly assumed that an `ErrorEvent` always contained a non-null `error`. This has been fixed, and our test coverage has been improved to cover this edge case. ### Fixed: Bun Shell & bun run with non-ascii cwd on Windows A bug affecting Bun Shell and `bun run` when run in a directory with non-ascii characters has been fixed thanks to [@dylan-conway](https://github.com/dylan-conway). ### Fixed: non-ascii characters in TypeScript enums An enum with non-ascii keys would get mangled. This has been fixed. ```ts#unicode-enum.ts enum X { a, b, รง, } console.log(X); ``` ### Fixed: Assertion failure with experimental decorator on abstract property An assertion failure would occur when using an experimental TypeScript decorator on an abstract property. This has been fixed, thanks to [@forcefieldsovereign](https://github.com/forcefieldsovereign). ### Fixed: ZWJ and ZWNJ characters in transpiler A crash that would occur when a file contained a Zero Width Joiner (ZWJ) or Zero Width Non-Joiner (ZWNJ) character inside of a property name has been fixed. ### Fixed: Crash in `module.mock` An edge case with using `module.mock` on modules that previously failed to load causing a crash has been fixed thanks to [@paperclover](https://github.com/paperclover). ### Fixed: `process.execArgv` `process.execArgv` lets you return arguments passed to the Bun runtime, in comparison to the program arguments in `process.argv`. In certain cases, non-runtime parameters were mistakenly included. Thanks to [@paperclover](https://github.com/paperclover) for fixing this. ### Fixed: Ignore optional dependencies that do not exist Before, installing the package `@laihoe/demoparser2` would fail due to an optional dependency on a package that was never published to NPM. Bun now matches `npm`'s behavior by simply ignoring these missing packages, since they are declared as optional dependencies. Thanks to [@dylan-conway](https://github.com/dylan-conway) ### Fixed: N-API modules re-assigning `module.exports` A bug where Bun incorrectly handled N-API modules that re-assigned `module.exports` has been fixed. Previously, Bun would ignore the return value of the module, causing the module to not be loaded correctly. This has been fixed, and Bun now correctly loads N-API modules that re-assign `module.exports`. This waas most noticable when `module.exports` was assigned to a function. Along the way, we've also fixed a potential crash when loading N-API modules that take a long time to initialize. ### Fixed: `bun:sqlite`'s `changes` field always 0 in statement.run() A bug in prepared statements caused `db.prepare(...).run(...)` to return 0 in certain cases instead of the number of changes from the statement. `db.run(...)` was not affected. ### Fixed: `bun patch` in workspace packages Bugs related to `bun patch --commit` diffing files in nested `node_modules` directories causing patch failures have been fixed. Thanks to [@zackradisic](https://github.com/zackradisic) ### Internal: Bun updated Zig to version 0.13 In [#9965](https://github.com/oven-sh/bun/pull/9965), Bun was upgraded to use the latest release of the Zig compiler. This makes Bun easier to contribute to, as there are a handful of language server, build system, and overall code quality improvements. Bug fixes within the Zig standard library have fixed some bugs in Bun; most notably the Windows [fix for handling WTF-16](https://github.com/ziglang/zig/pull/19005) (a looser version of UTF-16) within paths and environment. This fixes some rare edge cases where the error `InvalidUTF8` was reported with very little context. Thanks to [@squeek502](https://github.com/squeek502). One important build system improvement for the team and contributors is the ability to ensure that all platforms (Linux, Mac, and Windows) compile successfully without having to wait for CI to finish running. Contributors can now test-compile the code for all targets with `bun run zig-check` in the Bun repository.  ### Thanks to 9 contributors! - [@bomberstudios](https://github.com/bomberstudios) - [@dylan-conway](https://github.com/dylan-conway) - [@Eckhardt-D](https://github.com/Eckhardt-D) - [@exoego](https://github.com/exoego) - [@forcefieldsovereign](https://github.com/forcefieldsovereign) - [@Jarred-Sumner](https://github.com/Jarred-Sumner) - [@mohiwalla](https://github.com/mohiwalla) - [@paperclover](https://github.com/paperclover) - [@surprisedpika](https://github.com/surprisedpika) - [@zackradisic](https://github.com/zackradisic)In the next version of Bun
— Jarred Sumner (@jarredsumner) June 19, 2024
`Buffer.from(str, "base64")` gets 6x - 30x faster on large input, thanks to @lemire's simdutf pic.twitter.com/iFgI0Vv3sQ