Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://www.peterbe.com/rss.xml

  1. <?xml version="1.0" encoding="utf-8"?>
  2. <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Peterbe.com</title><link>http://www.peterbe.com/rss.xml</link><description>Stuff in Peter's head</description><atom:link href="http://www.peterbe.com/rss.xml" rel="self"/><language>en-us</language><lastBuildDate>Wed, 29 Apr 2026 12:22:01 +0000</lastBuildDate><item><title>Bun WebView is eating up my tmp storage</title><link>http://www.peterbe.com/plog/bun-webview-is-eating-up-my-tmp-storage</link><description>Bun WebView API creates tmp files that are large. It can eat your disk</description><pubDate>Wed, 29 Apr 2026 12:22:01 +0000</pubDate><guid>http://www.peterbe.com/plog/bun-webview-is-eating-up-my-tmp-storage</guid></item><item><title>html-getter - A powerfully simple HTML scraper in Bun</title><link>http://www.peterbe.com/plog/html-getter</link><description>&lt;p&gt;When &lt;a href="https://bun.com/blog/bun-v1.3.12"&gt;Bun v1.3.12&lt;/a&gt; was released last week, they subtly included a powerful feature, almost under the radar: &lt;code&gt;WebView&lt;/code&gt;. It's like Playwright/Puppeteer but more limited, especially in terms of documentation.&lt;/p&gt;
  3. &lt;p&gt;I built a demo app based on it called &lt;a href="https://github.com/peterbe/html-getter"&gt;html-getter&lt;/a&gt; which you can use like this:&lt;/p&gt;
  4. &lt;pre&gt;&lt;code class="hljs"&gt;
  5. bun run src/html-getter.ts https://www.peterbe.com
  6. &lt;/code&gt;&lt;/pre&gt;
  7.  
  8. &lt;p&gt;That will open &lt;code&gt;https://www.peterbe.com&lt;/code&gt; with Chrome or Chromium or WebKit and evaluate the following JavaScript expression: &lt;code&gt;document.documentElement.outerHTML&lt;/code&gt; (which is the whole HTML source of the whole DOM) and print this to stdout.&lt;/p&gt;
  9. &lt;p&gt;or you can use it like this:&lt;/p&gt;
  10. &lt;pre&gt;&lt;code class="hljs"&gt;
  11. bun run src/html-getter.ts --body --screenshot /tmp/page.png https://www.peterbe.com
  12. &lt;/code&gt;&lt;/pre&gt;
  13.  
  14. &lt;p&gt;which means it prints everything inside the &lt;code&gt;&amp;lt;body&amp;gt;...&amp;lt;/body&amp;gt;&lt;/code&gt; instead and at the same time, it dumps a screenshot of what it looks like, which can be useful for debugging.&lt;/p&gt;
  15. &lt;p&gt;What's cool about this is that you no longer need to install &lt;code&gt;playwright&lt;/code&gt; or &lt;code&gt;puppeteer&lt;/code&gt;. Scraping HTML is just one of many applications you can use &lt;code&gt;WebView&lt;/code&gt; for. I wouldn't use it for automated headless browser testing though because the documentation, tooling, and APIs for Playwright is still so much much better.&lt;/p&gt;
  16. &lt;p&gt;&lt;strong&gt;WARNING&lt;/strong&gt;&lt;/p&gt;
  17. &lt;p&gt;At the time of writing this, I am unable, on macOS, to compile this Bun script into a binary. When I do, this happens:&lt;/p&gt;
  18. &lt;pre&gt;&lt;code class="hljs"&gt;
  19. $ bun run build
  20. $ bun build src/html-getter.ts --target=bun --outfile out/html-getter --compile --bytecode
  21.  [14ms]  bundle  1 modules
  22.  [77ms] compile  out/html-getter
  23. $ ./out/html-getter https://www.peterbe.com
  24. [1]    70304 killed     ./out/html-getter https://www.peterbe.com
  25. &lt;/code&gt;&lt;/pre&gt;
  26.  
  27. &lt;p&gt;The same worked on my x64 Linux server, but to get this to compile on macOS might need some more careful thought.&lt;/p&gt;</description><pubDate>Fri, 17 Apr 2026 13:34:17 +0000</pubDate><guid>http://www.peterbe.com/plog/html-getter</guid></item><item><title>Bestest security tip for updating packages with Bun</title><link>http://www.peterbe.com/plog/bestest-security-tip-for-updating-packages-with-bun</link><description>&lt;p&gt;I don't know when this was added but if you use Bun in your TypeScript project, you might be familiar with &lt;code&gt;bun upgrade&lt;/code&gt; which is a CLI tool for upgrading the packages you pin and depend on. You can now pass it a "cool down period" which means a certain package update doesn't count unless it's been published for at least X hours.&lt;/p&gt;
  28. &lt;p&gt;&lt;strong&gt;This is critical for avoiding installing compromised NPM packages.&lt;/strong&gt; Sometimes a package gets hacked. If you were to be unlucky and upgrade to it at that window of time, you can have pinned an insecure/compromised version into your lock file.
  29. When the &lt;a href="https://www.trendmicro.com/en_us/research/26/c/axios-npm-package-compromised.html"&gt;Axios supply chain attack&lt;/a&gt; happened, there was a 39 minute window when installing the latest version of &lt;code&gt;axios&lt;/code&gt; would (potentially) sneak in the bad package version.&lt;/p&gt;
  30. &lt;p&gt;Now, this is how I use &lt;code&gt;bun update&lt;/code&gt;:&lt;/p&gt;
  31. &lt;pre&gt;&lt;code class="hljs"&gt;
  32. bun update --interactive --minimum-release-age=86400
  33. &lt;/code&gt;&lt;/pre&gt;
  34.  
  35. &lt;p&gt;That means, it won't upgrade anything that hasn't sat for at least 1 day.&lt;/p&gt;</description><pubDate>Tue, 14 Apr 2026 14:25:40 +0000</pubDate><guid>http://www.peterbe.com/plog/bestest-security-tip-for-updating-packages-with-bun</guid></item><item><title>pytest "import file mismatch"</title><link>http://www.peterbe.com/plog/pytest-import-file-mismatch</link><description>Make sure your test files in a pytest tested project sit in directories with a __init__.py</description><pubDate>Wed, 01 Apr 2026 13:20:53 +0000</pubDate><guid>http://www.peterbe.com/plog/pytest-import-file-mismatch</guid></item><item><title>Copy the current line in VS Code</title><link>http://www.peterbe.com/plog/copy-the-current-line-in-vs-code</link><description>In VS Code you can copy the current line without first selecting it. Cmd-C without selection defaults to whole line.</description><pubDate>Thu, 12 Mar 2026 15:07:52 +0000</pubDate><guid>http://www.peterbe.com/plog/copy-the-current-line-in-vs-code</guid></item><item><title>logger.error or logger.exception in Python</title><link>http://www.peterbe.com/plog/logger.error-or-logger.exception</link><description>&lt;p&gt;Consider this Python code:&lt;/p&gt;
  36. &lt;pre&gt;&lt;code class="hljs"&gt;
  37. &lt;span class="hljs-keyword"&gt;try&lt;/span&gt;:
  38.    &lt;span class="hljs-number"&gt;1&lt;/span&gt; / &lt;span class="hljs-number"&gt;0&lt;/span&gt;
  39. &lt;span class="hljs-keyword"&gt;except&lt;/span&gt; Exception &lt;span class="hljs-keyword"&gt;as&lt;/span&gt; e:
  40.    logger.error(&lt;span class="hljs-string"&gt;&amp;quot;An error occurred while dividing by zero.: %s&amp;quot;&lt;/span&gt;, e)
  41. &lt;/code&gt;&lt;/pre&gt;
  42.  
  43. &lt;p&gt;The output of this is:&lt;/p&gt;
  44. &lt;pre&gt;&lt;code class="hljs"&gt;
  45. An error occurred while dividing by zero.: division by zero
  46. &lt;/code&gt;&lt;/pre&gt;
  47.  
  48. &lt;p&gt;No traceback. Perhaps you don't care because you don't need it.&lt;br /&gt;
  49. I see code like this quite often and it's curious that you even use &lt;code&gt;logger.error&lt;/code&gt; if it's not a problem. And it's curious that you include the stringified exception into the logger message.&lt;/p&gt;
  50. &lt;p&gt;Another common pattern I see is use of &lt;code&gt;exc_info=True&lt;/code&gt; like this:&lt;/p&gt;
  51. &lt;pre&gt;&lt;code class="hljs"&gt;
  52. &lt;span class="hljs-keyword"&gt;try&lt;/span&gt;:
  53.    &lt;span class="hljs-number"&gt;1&lt;/span&gt; / &lt;span class="hljs-number"&gt;0&lt;/span&gt;
  54. &lt;span class="hljs-keyword"&gt;except&lt;/span&gt; Exception:
  55.    logger.error(&lt;span class="hljs-string"&gt;&amp;quot;An error occurred while dividing by zero.&amp;quot;&lt;/span&gt;, exc_info=&lt;span class="hljs-literal"&gt;True&lt;/span&gt;)
  56. &lt;/code&gt;&lt;/pre&gt;
  57.  
  58. &lt;p&gt;Its output is:&lt;/p&gt;
  59. &lt;pre&gt;&lt;code class="hljs"&gt;
  60. An error occurred while dividing by zero.
  61. Traceback (most recent call last):
  62.  File &amp;quot;/Users/peterbengtsson/dummy.py&amp;quot;, line 23, in &amp;lt;module&amp;gt;
  63.    1 / 0
  64.    ~~^~~
  65. ZeroDivisionError: division by zero
  66. &lt;/code&gt;&lt;/pre&gt;
  67.  
  68. &lt;p&gt;Ok, now you get the traceback and the error value (&lt;code&gt;division by zero&lt;/code&gt; in this case).&lt;/p&gt;
  69. &lt;p&gt;But a more convenient function is &lt;code&gt;logger.exception&lt;/code&gt; which looks like this:&lt;/p&gt;
  70. &lt;pre&gt;&lt;code class="hljs"&gt;
  71. &lt;span class="hljs-keyword"&gt;try&lt;/span&gt;:
  72.    &lt;span class="hljs-number"&gt;1&lt;/span&gt; / &lt;span class="hljs-number"&gt;0&lt;/span&gt;
  73. &lt;span class="hljs-keyword"&gt;except&lt;/span&gt; Exception:
  74.    logger.exception(&lt;span class="hljs-string"&gt;&amp;quot;An error occurred while dividing by zero.&amp;quot;&lt;/span&gt;)
  75. &lt;/code&gt;&lt;/pre&gt;
  76.  
  77. &lt;p&gt;Its output is:&lt;/p&gt;
  78. &lt;pre&gt;&lt;code class="hljs"&gt;
  79. An error occurred while dividing by zero.
  80. Traceback (most recent call last):
  81.  File &amp;quot;/Users/peterbengtsson/dummy.py&amp;quot;, line 9, in &amp;lt;module&amp;gt;
  82.    1 / 0
  83.    ~~^~~
  84. ZeroDivisionError: division by zero
  85. &lt;/code&gt;&lt;/pre&gt;
  86.  
  87. &lt;p&gt;So it's sugar for &lt;code&gt;logger.error&lt;/code&gt;.&lt;/p&gt;
  88. &lt;p&gt;Also, a common logging config is something like this:&lt;/p&gt;
  89. &lt;pre&gt;import logging
  90.  
  91. logger = logging.getLogger(__name__)
  92. logging.basicConfig(
  93.    format=&amp;quot;%(asctime)s - %(levelname)s - %(name)s - %(message)s&amp;quot;, level=logging.ERROR
  94. )&lt;/pre&gt;
  95.  
  96. &lt;p&gt;So if you use &lt;code&gt;logger.exception&lt;/code&gt; what will it print? In short, the same as if you used &lt;code&gt;logger.error&lt;/code&gt;. For example, with the &lt;code&gt;logger.exception("An error occurred while dividing by zero.")&lt;/code&gt; line above:&lt;/p&gt;
  97. &lt;pre&gt;&lt;code class="hljs"&gt;
  98. 2026-03-06 10:45:23,570 - ERROR - __main__ - An error occurred while dividing by zero.
  99. Traceback (most recent call last):
  100.  File &amp;quot;/Users/peterbengtsson/dummy.py&amp;quot;, line 12, in &amp;lt;module&amp;gt;
  101.    1 / 0
  102.    ~~^~~
  103. ZeroDivisionError: division by zero
  104. &lt;/code&gt;&lt;/pre&gt;
  105.  
  106. &lt;h3 id="bonus-add_note"&gt;&lt;a class="toclink" href="#bonus-add_note"&gt;Bonus - &lt;code&gt;add_note&lt;/code&gt;&lt;/a&gt;&lt;/h3&gt;
  107. &lt;p&gt;You can, if it's applicable, inject some more information about the exception. Consider:&lt;/p&gt;
  108. &lt;pre&gt;&lt;code class="hljs"&gt;
  109. &lt;span class="hljs-keyword"&gt;try&lt;/span&gt;:
  110.    n / &lt;span class="hljs-number"&gt;0&lt;/span&gt;
  111. &lt;span class="hljs-keyword"&gt;except&lt;/span&gt; Exception &lt;span class="hljs-keyword"&gt;as&lt;/span&gt; exception:
  112.    exception.add_note(&lt;span class="hljs-string"&gt;f&amp;quot;The numerator was &lt;span class="hljs-subst"&gt;{n}&lt;/span&gt;.&amp;quot;&lt;/span&gt;)
  113.    logger.exception(&lt;span class="hljs-string"&gt;&amp;quot;An error occurred while dividing by zero.&amp;quot;&lt;/span&gt;)
  114. &lt;/code&gt;&lt;/pre&gt;
  115.  
  116. &lt;p&gt;The net output of this is:&lt;/p&gt;
  117. &lt;pre&gt;&lt;code class="hljs"&gt;
  118. 2026-03-06 10:48:34,279 - ERROR - __main__ - An error occurred while dividing by zero.
  119. Traceback (most recent call last):
  120.  File &amp;quot;/Users/peterbengtsson/dummy.py&amp;quot;, line 13, in &amp;lt;module&amp;gt;
  121.    1 / 0
  122.    ~~^~~
  123. ZeroDivisionError: division by zero
  124. The numerator was 123.
  125. &lt;/code&gt;&lt;/pre&gt;</description><pubDate>Fri, 06 Mar 2026 15:27:44 +0000</pubDate><guid>http://www.peterbe.com/plog/logger.error-or-logger.exception</guid></item><item><title>How to find which git SHA it was when you merged in the default branch</title><link>http://www.peterbe.com/plog/how-to-find-which-git-sha-it-was-when-you-merged-in-the-default-branch</link><description>&lt;p&gt;Please tell me there's a better way.&lt;/p&gt;
  126. &lt;p&gt;I'm in a git feature branch. It was branched off of &lt;code&gt;master&lt;/code&gt; some time ago. Then I made some commits. Later, I merged in latest &lt;code&gt;master&lt;/code&gt;, and after that some more commits. The question is what was the SHA when I merged in latest &lt;code&gt;master&lt;/code&gt;? How to find that out?&lt;/p&gt;
  127. &lt;p&gt;Here's what I did:&lt;/p&gt;
  128. &lt;p&gt;I'm in my feature branch and I run:&lt;/p&gt;
  129. &lt;pre&gt;&lt;code class="hljs"&gt;
  130. git &lt;span class="hljs-built_in"&gt;log&lt;/span&gt; --merges --first-parent
  131. &lt;/code&gt;&lt;/pre&gt;
  132.  
  133. &lt;p&gt;It prints this out:&lt;/p&gt;
  134. &lt;pre&gt;&lt;code class="hljs"&gt;
  135. commit 2c010ef6e94d792f25f7309ed83a2d35e41e5051
  136. Merge: 24b2a2513d6f e2817859ed02
  137. Author: Peter Bengtsson &amp;lt;email&amp;gt;
  138. Date:   Thu Feb 26 14:06:24 2026 +0000
  139.  
  140.  Merge remote-tracking branch &amp;#x27;origin&amp;#x27; into name-of-my-feature-branch
  141. &lt;/code&gt;&lt;/pre&gt;
  142.  
  143. &lt;p&gt;The SHA that was, on &lt;code&gt;master&lt;/code&gt;, at the time of merging, was &lt;code&gt;e2817859ed02&lt;/code&gt; which is the second thing the &lt;code&gt;Merge: 24b2a2513d6f e2817859ed02&lt;/code&gt; line.&lt;/p&gt;
  144. &lt;p&gt;Now, equipped with this I can go back in time &lt;code&gt;git checkout e2817859ed02&lt;/code&gt; and on that detached HEAD, I can do things like run (unit) tests to see if the &lt;code&gt;master&lt;/code&gt; branch was busted at the time I merged it into my feature branch.&lt;/p&gt;</description><pubDate>Thu, 26 Feb 2026 17:23:04 +0000</pubDate><guid>http://www.peterbe.com/plog/how-to-find-which-git-sha-it-was-when-you-merged-in-the-default-branch</guid></item><item><title>gg2 branches got 50% faster by a Promise.all</title><link>http://www.peterbe.com/plog/gg2-branches-got-50percent-faster-by-a-promise.all</link><description>&lt;p&gt;&lt;a href="https://gg2.peterbe.com/"&gt;gg2&lt;/a&gt; is a command line tool for doing things with Git branches, faster. One of the convenient commands is &lt;code&gt;gg2 branches&lt;/code&gt;.
  145. It lists your recent branches, sorted by committer-date and for each branch it displays a human-friendly date distance and whether it's already been merged. Looks like this:&lt;/p&gt;
  146. &lt;p&gt;&lt;a href="/cache/d9/44/d94443c94b1f1d57abc02f7d4dcb717c.png"&gt;&lt;img src="/cache/d9/44/d94443c94b1f1d57abc02f7d4dcb717c.png" class="fullsize"&gt;&lt;/a&gt;&lt;/p&gt;
  147. &lt;p&gt;Turns out, for large repos figuring out which branches have already been merged is quite slow. For example, in this repo it takes half a second to list all merged branches:&lt;/p&gt;
  148. &lt;pre&gt;&lt;code class="hljs"&gt;
  149. $ git branch --all --merged | wc -l
  150. 669
  151.  
  152. $ time git branch --all --merged 1&amp;gt;/dev/null
  153.  
  154. real    0m0.490s
  155. user    0m0.460s
  156. sys     0m0.030s
  157. &lt;/code&gt;&lt;/pre&gt;
  158.  
  159. &lt;p&gt;The problem was that &lt;code&gt;gg2 branches&lt;/code&gt; also does multiple other &lt;code&gt;git branch&lt;/code&gt; listing commands to get information. In particular: get the current branch, figure out the default branch, a list of branch committer dates, and a list of merged branches.&lt;br /&gt;
  160. All of these async operations were done in serial. With a bit of rearranging, and refactoring, all of these can be turned into this:&lt;/p&gt;
  161. &lt;pre&gt;&lt;code class="hljs"&gt;
  162. &lt;span class="hljs-keyword"&gt;const&lt;/span&gt; [defaultBranch, currentBranch, dates, isMerged] = &lt;span class="hljs-keyword"&gt;await&lt;/span&gt; &lt;span class="hljs-title class_"&gt;Promise&lt;/span&gt;.&lt;span class="hljs-title function_"&gt;all&lt;/span&gt;([
  163.  &lt;span class="hljs-title function_"&gt;getDefaultBranch&lt;/span&gt;(git),
  164.  &lt;span class="hljs-title function_"&gt;getCurrentBranch&lt;/span&gt;(git),
  165.  &lt;span class="hljs-title function_"&gt;getAllBranchDates&lt;/span&gt;(git),
  166.  &lt;span class="hljs-title function_"&gt;getAllMergedBranches&lt;/span&gt;(git),
  167. ])
  168. &lt;/code&gt;&lt;/pre&gt;
  169.  
  170. &lt;p&gt;The &lt;code&gt;getAllMergedBranches(git)&lt;/code&gt; function still takes a very long time and I think it lists all remote branches that have been merged. Anyway, now it's only the slowest part of the &lt;code&gt;Promise.all&lt;/code&gt; rather than one of multiple.&lt;/p&gt;
  171. &lt;p&gt;&lt;strong&gt;UPDATE&lt;/strong&gt;&lt;/p&gt;
  172. &lt;p&gt;The act of blogging about something can sometimes bring out how wrong you are.&lt;br /&gt;
  173. What I didn't realize is that I was using &lt;code&gt;git branch --all --merged&lt;/code&gt; to know which local branches have already been merged into the default branch. But you can just use &lt;code&gt;git branch --merged&lt;/code&gt; to get the same result but much much faster.&lt;/p&gt;
  174. &lt;p&gt;&lt;a href="https://github.com/peterbe/gg2/pull/101"&gt;Correcting for this&lt;/a&gt;, on a large repo, the average time to execute &lt;code&gt;gg2 branches&lt;/code&gt; went from median 541ms to median 188ms. So that's 3x speed improvement.&lt;/p&gt;</description><pubDate>Mon, 16 Feb 2026 13:17:09 +0000</pubDate><guid>http://www.peterbe.com/plog/gg2-branches-got-50percent-faster-by-a-promise.all</guid></item><item><title>xbar-my-prs Info about your GitHub PRs in the macOS menu bar</title><link>http://www.peterbe.com/plog/xbar-my-prs</link><description>&lt;p&gt;&lt;a href="https://github.com/peterbe/xbar-my-prs"&gt;xbar-my-prs&lt;/a&gt; is a plugin I wrote for something called &lt;a href="https://xbarapp.com/"&gt;xbar&lt;/a&gt; which is a macOS app that let's you write scripts that then show up in the macOS menu bar. Mine is about fetching information about my recent GitHub pull requests.&lt;/p&gt;
  175. &lt;p&gt;A picture of it in action:&lt;/p&gt;
  176. &lt;p&gt;&lt;a href="/cache/b8/f6/b8f6c9b52314c6a7674ac86d44fc8a46.png"&gt;&lt;img src="/cache/b8/f6/b8f6c9b52314c6a7674ac86d44fc8a46.png" class="fullsize" style="width:70%"&gt;&lt;/a&gt;&lt;/p&gt;
  177. &lt;p&gt;Every minute, it does this GitHub search: &lt;a href="https://github.com/search?q=is%3Apr+is%3Aopen+author%3A%40me+sort%3Aupdated+&amp;amp;type=pullrequests"&gt;&lt;code&gt;is:pr author:@me sort:updated&lt;/code&gt;&lt;/a&gt;&lt;/p&gt;
  178. &lt;p&gt;Then it parses the results and attempts to display a neat summary.&lt;/p&gt;
  179. &lt;p&gt;And each time it runs, it stores a copy of the result in the &lt;code&gt;/tmp&lt;/code&gt; directory so that it can compare what the result became compared to before. So if something has changed in the last minute, it displays a summary of the change(s). Example:&lt;/p&gt;
  180. &lt;p&gt;&lt;a href="/cache/d5/d5/d5d5ee05f145495eb912840129a5b20b.png"&gt;&lt;img src="/cache/d5/d5/d5d5ee05f145495eb912840129a5b20b.png" class="fullsize" style="width:60%"&gt;&lt;/a&gt;&lt;/p&gt;
  181. &lt;h3 id="how-you-can-get-it-too"&gt;&lt;a class="toclink" href="#how-you-can-get-it-too"&gt;How you can get it too&lt;/a&gt;&lt;/h3&gt;
  182. &lt;p&gt;First you have to install &lt;a href="https://xbarapp.com/"&gt;xbar&lt;/a&gt; onto your macOS.&lt;/p&gt;
  183. &lt;p&gt;At the time of writing you can't install it with Homebrew. Working on that. But all you need is &lt;code&gt;just&lt;/code&gt; and Bun and then you can install it like this:&lt;/p&gt;
  184. &lt;pre&gt;&lt;code class="hljs"&gt;
  185. git &lt;span class="hljs-built_in"&gt;clone&lt;/span&gt; https://github.com/peterbe/xbar-my-prs.git &amp;amp;&amp;amp; &lt;span class="hljs-built_in"&gt;cd&lt;/span&gt; xbar-my-prs
  186. just install
  187. just ship
  188. &lt;/code&gt;&lt;/pre&gt;
  189.  
  190. &lt;p&gt;If all goes well, it should have crated an executable file at:&lt;/p&gt;
  191. &lt;pre&gt;&lt;code class="hljs"&gt;
  192. ~/Library/Application\ Support/xbar/plugins/my-prs.1m.bin
  193. &lt;/code&gt;&lt;/pre&gt;
  194.  
  195. &lt;p&gt;on your system. And that should be all xbar needs to know there's a new plugin to run.&lt;/p&gt;</description><pubDate>Thu, 29 Jan 2026 18:37:54 +0000</pubDate><guid>http://www.peterbe.com/plog/xbar-my-prs</guid></item><item><title>Optimizing Bun compiled binary for gg2</title><link>http://www.peterbe.com/plog/optimizing-bun-compiled-binary-for-gg2</link><description>&lt;p&gt;&lt;strong&gt;tl;dr; adding &lt;code&gt;--bytecode&lt;/code&gt; and &lt;code&gt;--production&lt;/code&gt; to &lt;code&gt;bun build --compile&lt;/code&gt; gives a marginal boost.&lt;/strong&gt;&lt;/p&gt;
  196. &lt;p&gt;I have a CLI tool called &lt;a href="https://gg2.peterbe.com/"&gt;gg2&lt;/a&gt; which is written in TypeScript and using Bun &lt;strong&gt;compiled to a single executable binary&lt;/strong&gt; that can be &lt;a href="https://www.peterbe.com/plog/gg2-is-now-installable-with-homebrew"&gt;installed with Homebrew&lt;/a&gt;. It's fast. &lt;a href="https://www.peterbe.com/plog/gg2-is-now-installable-with-homebrew"&gt;Only 17% slower than GitHub's Go-compile &lt;code&gt;gh&lt;/code&gt; CLI&lt;/a&gt;. But can it get even faster?&lt;/p&gt;
  197. &lt;p&gt;I read about &lt;a href="https://bun.com/docs/bundler/bytecode"&gt;Bytecode Caching&lt;/a&gt; which is supposed to make the executable "dramatically improved". Hmm. Let's see. There's also the &lt;code&gt;--production&lt;/code&gt; option, which according to &lt;code&gt;Set NODE_ENV=production and enable minification&lt;/code&gt;. Not convinced it's doing much but let's try.&lt;/p&gt;
  198. &lt;p&gt;I compiled the binary 4 different ways:&lt;/p&gt;
  199. &lt;ul&gt;
  200. &lt;li&gt;&lt;code&gt;bun build src/index.ts --target=bun --compile --outfile out/gg&lt;/code&gt;&lt;/li&gt;
  201. &lt;li&gt;&lt;code&gt;bun build src/index.ts --target=bun --compile --outfile out/gg-bytecode --bytecode&lt;/code&gt;&lt;/li&gt;
  202. &lt;li&gt;&lt;code&gt;bun build src/index.ts --target=bun --compile --outfile out/gg-production --production&lt;/code&gt;&lt;/li&gt;
  203. &lt;li&gt;&lt;code&gt;bun build src/index.ts --target=bun --compile --outfile out/gg-bytecode-production --production --bytecode&lt;/code&gt;&lt;/li&gt;
  204. &lt;/ul&gt;
  205. &lt;p&gt;Then I ran &lt;code&gt;hyperfine&lt;/code&gt; like this:&lt;/p&gt;
  206. &lt;pre&gt;&lt;code class="hljs"&gt;
  207. hyperfine &amp;quot;./out/gg --version&amp;quot; &amp;quot;./out/gg-bytecode --version&amp;quot; &amp;quot;./out/gg-production --version&amp;quot; &amp;quot;./out/gg-bytecode-production --version&amp;quot; --warmup 6
  208. &lt;/code&gt;&lt;/pre&gt;
  209.  
  210. &lt;p&gt;The results are as follows:&lt;/p&gt;
  211. &lt;table&gt;
  212. &lt;thead&gt;
  213. &lt;tr&gt;
  214. &lt;th&gt;BINARY&lt;/th&gt;
  215. &lt;th&gt;TIME (ms, smaller is better)&lt;/th&gt;
  216. &lt;th&gt;SIZE (MB)&lt;/th&gt;
  217. &lt;/tr&gt;
  218. &lt;/thead&gt;
  219. &lt;tbody&gt;
  220. &lt;tr&gt;
  221. &lt;td&gt;gg&lt;/td&gt;
  222. &lt;td&gt;87&lt;/td&gt;
  223. &lt;td&gt;58&lt;/td&gt;
  224. &lt;/tr&gt;
  225. &lt;tr&gt;
  226. &lt;td&gt;gg-bytecode&lt;/td&gt;
  227. &lt;td&gt;81&lt;/td&gt;
  228. &lt;td&gt;60&lt;/td&gt;
  229. &lt;/tr&gt;
  230. &lt;tr&gt;
  231. &lt;td&gt;gg-production&lt;/td&gt;
  232. &lt;td&gt;82.4&lt;/td&gt;
  233. &lt;td&gt;55&lt;/td&gt;
  234. &lt;/tr&gt;
  235. &lt;tr&gt;
  236. &lt;td&gt;gg-bytecode-production&lt;/td&gt;
  237. &lt;td&gt;79.6&lt;/td&gt;
  238. &lt;td&gt;60&lt;/td&gt;
  239. &lt;/tr&gt;
  240. &lt;/tbody&gt;
  241. &lt;/table&gt;
  242. &lt;p&gt;&lt;a href="/cache/c7/1f/c71f48b8b4ab4acb5c455a140d0301da.png"&gt;&lt;img src="/cache/c7/1f/c71f48b8b4ab4acb5c455a140d0301da.png" class="fullsize"&gt;&lt;/a&gt;&lt;/p&gt;
  243. &lt;p&gt;(&lt;em&gt;sorry for being terrible at using Excel to draw charts&lt;/em&gt;)&lt;/p&gt;
  244. &lt;h3 id="conclusion"&gt;&lt;a class="toclink" href="#conclusion"&gt;Conclusion&lt;/a&gt;&lt;/h3&gt;
  245. &lt;p&gt;I'm skeptical. The &lt;code&gt;hyperfine&lt;/code&gt; often complains about statistical outliers so you have to run it with warmup and re-run it till it doesn't complain.&lt;/p&gt;
  246. &lt;p&gt;One caveat with using &lt;code&gt;--bytecode&lt;/code&gt; is that the compiled code is not re-usable across &lt;strong&gt;different versions of bun&lt;/strong&gt; but I don't understand how that's applicable if it's a executable binary that is shipped outside of Bun.&lt;/p&gt;
  247. &lt;p&gt;I'm going to add &lt;code&gt;--bytecode&lt;/code&gt; and &lt;code&gt;--production&lt;/code&gt; to the next release of &lt;a href="https://github.com/peterbe/gg2"&gt;&lt;code&gt;gg2&lt;/code&gt;&lt;/a&gt;.&lt;/p&gt;</description><pubDate>Tue, 13 Jan 2026 16:06:09 +0000</pubDate><guid>http://www.peterbe.com/plog/optimizing-bun-compiled-binary-for-gg2</guid></item></channel></rss>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//www.peterbe.com/rss.xml

Home · About · News · Docs · Terms

 
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda