v1.1.14 fixes 63 bugs (addressing 519 👍). Patch node_modules withbun patch. ORM-less object mapping inbun:sqlite. Log allfetch() calls as acurl command. Node.js compatibility improvements. bun install bugfixes,bun:sqlite bugfixes, Windows bugfixes. And more.
v1.1.10 fixes 20 bugs. 2x faster uncached bun install on Windows.fetch() uses up to 2.8x less memory. Several bugfixes to bun install, sourcemaps, Windows reliability improvements and Node.js compatibility improvements
bun install now supports authenticating via ssh to install dependencies from private git repositories. These are cloned using your git SSH key viagit clone.
bun i git@github.com:paperclover/secret-utilities.git
This makesbun install easier to use when working with private repositories from Gitlab, Bitbucket, or other git hosting services. GitHub repositories were sometimes impacted by this issue, but less frequently.
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.
bun build src/app.tsx --outdir ./dist --sourcemap=linked --minify
This will produce the directorydist withapp.js andapp.js.map, and the comment//# sourceMappingURL=app.js.map to load the sourcemap for debugging.
When a WebSocket connection fails, the error event now includes amessage property with a more detailed error message.
const ws=newWebSocket("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:
WebSocket connection to'ws://localhost:8080/' failed: Failed to connect
Instead of only including relevant information in theclose event, theerror event on connection failure now includes amessage property with an error message.
When a WebSocket fails to connect, it emits both theerror andclose events.
const ws=newWebSocket("ws://localhost:8080");ws.addEventListener("error", (error)=> {// Connection error emitted});ws.addEventListener("close", ()=> {// Connection did not fully open, but it is still closed});
Previously, printingconsole.log(error) from a WebSocket connection error would sometimes cause a crash. The code incorrectly assumed that anErrorEvent always contained a non-nullerror. This has been fixed, and our test coverage has been improved to cover this edge case.
An assertion failure would occur when using an experimental TypeScript decorator on an abstract property. This has been fixed, thanks to@forcefieldsovereign.
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.
process.execArgv lets you return arguments passed to the Bun runtime, in comparison to the program arguments inprocess.argv. In certain cases, non-runtime parameters were mistakenly included. Thanks to@paperclover for fixing this.
Before, installing the package@laihoe/demoparser2 would fail due to an optional dependency on a package that was never published to NPM. Bun now matchesnpm's behavior by simply ignoring these missing packages, since they are declared as optional dependencies.
A bug where Bun incorrectly handled N-API modules that re-assignedmodule.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-assignmodule.exports. This waas most noticable whenmodule.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.
A bug in prepared statements causeddb.prepare(...).run(...) to return 0 in certain cases instead of the number of changes from the statement.db.run(...) was not affected.
In#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 Windowsfix for handling WTF-16 (a looser version of UTF-16) within paths and environment. This fixes some rare edge cases where the errorInvalidUTF8 was reported with very little context. Thanks to@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 withbun run zig-check in the Bun repository.