Jarred Sumner
@jarredsumner
Followers
131K
Following
25K
Media
4K
Statuses
25K
building @bunjavascript. formerly: @stripe (twice) @thielfellowship. high school dropout. npm i -g bun
San Francisco, CA
Joined May 2014
It's pretty cool how easy it is to bring 'use workflow' support to any framework It's built using standard request web apis, so all you have to do is create a route handler, pass the request and you're good to go For instance, this is 'use workflow' support in bun:
22
12
232
Instant relief, anytime — Mend+ Massager penetrates deep into tight muscles, melts away knots, and restores natural mobility within minutes.
0
0
8
Another approach would be to use “engines” but currently yarn v1 prints a loud warning for any package using an engine it doesn’t recognize, and yarn v1 predates bun so it doesn’t know what bun is.
2
0
16
honestly not a bad idea, as a way for npm packages to specify they should run in bun if available and fallback to node. keep the `#!/usr/bin/env node` for compatibility, and then no need for —bun flag for those packages
@jarredsumner @rickhanlonii “use bun”
7
0
107
Very excited for Vercel Ship tomorrow
23
5
383
A crash that impacted some Next.js projects when `next build` was used with Turbopack has been fixed. We were not reference-counting napi_env (which node does). Now we do too.
0
0
6
On Windows, there was a hang when running package.json scripts that could occur when non-ascii environment variables are used. Narrowing down the cause was difficult. This started in Bun v1.2.23 after we upgraded libuv (but wasn’t really libuv’s fault).
1
0
4
A URL heap size accounting bug was found thanks to Martin Schwarzl at Cloudflare. An integer underflow when creating large URL objects could lead to GC running a LOT more than it should be.
1
0
3
Several important bugfixes in this one.
Bun v1.3.1 - Fixes 103 issues (addressing 172 👍) - Faster `bun build` in symlink-heavy projects (especially on macOS) - Fixed Windows hang - bun test —pass-with-no-tests —only-failures - publicHoistPattern in bun install - Many bundler & runtime bugfixes https://t.co/yIOux3egRH
2
1
115
Bun v1.3.1 - Fixes 103 issues (addressing 172 👍) - Faster `bun build` in symlink-heavy projects (especially on macOS) - Fixed Windows hang - bun test —pass-with-no-tests —only-failures - publicHoistPattern in bun install - Many bundler & runtime bugfixes https://t.co/yIOux3egRH
bun.com
Fixes 103 issues (addressing 172 👍). 2× faster bun build on macOS for symlink-heavy projects, source maps preserve legal comments, and --format=cjs now inlines import.meta; bun test adds global vi,...
5
16
391
updated our docs!! 🥰 we now have dedicated sections for: • runtime • package manager • bundler • test runner
44
41
1K
probably going to start running Claude on every issue to find duplicates or attempt to reproduce.
2
0
26
there are an insane number of duplicates, but many take a lot of time to figure out if it is a duplicate and which one. I don’t blame people for not finding duplicates, in many cases it’s not clear without knowing the code. and useful reproductions are rare.
2
0
24
properly triaging and coming up with reproductions for GitHub issues in bun’s repo could fill >1 full-time job of time need to experiment more with process changes to make this faster
8
0
73
sometimes when Claude is unsure I remind it “you are AGI”
58
23
821
Bun v1.3.1 ships on Friday at 8:00am BST (Bun standard time)
29
6
464
There are still issues that only happen on Windows. There are also issues that only happen on macOS or Linux. More on Windows, though we also enable more assertions on Windows.
1
0
29
So like configuration version 1.3 would have linker = “isolated” when workspaces are in use. Then existing users from < 1.2 wouldn’t have changes.
3
1
21
I think the main thing we did wrong here was not store a “configuration version”. Rails does a good job of this - track what version to use for default settings. Then we can change defaults in future versions without impacting existing users
1
1
29
We’ve heard from a number of users that making isolated installs the default for workspaces in bun v1.3 caused issues Should we revert back to hoisted as a default & revisit in a future version after a better migration path?
16
1
43