Choosing Between Bun.serve() and External Frameworks for API Development
Decide between Bun.serve() and external frameworks like Express. Learn when to prioritize raw Zig-powered performance over middleware convenience for your API.
Loading…
ReadMeFeed / Community knowledge
Bun
Real questions. Useful conversations. Find the people who know your stack.
Bun
Languages & runtimes · #bun
javascriptHow to safely upgrade Bun and roll back to a previous version
When managing a Bun installation in a development or production environment, what are the recommended steps to upgrade to a new stable or canary release while ensuring the ability to verify the update and roll back to a known good version if issues arise? Please outline any verification commands, version‑checking procedures, and rollback strategies that are
How does Bun handle safe upgrades and rollbacks?
When managing a Bun installation, what steps ensure a safe upgrade to a new stable or canary release, and how can you verify that the upgrade succeeded? If an issue arises after upgrading, what procedures does Bun provide (or recommend) for rolling back to a previous version, and what precautions should be taken to avoid breaking existing projects during thi
How to validate backup and restore operations using Bun's file I/O APIs?
Bun provides an all‑in‑one toolkit with fast built‑in tools and file I/O APIs (e.g., Bun.file ) that can be used to read, write, and verify data. When designing a backup and restore workflow, what steps should be taken to ensure the backup is correct and the restore reproduces the original state? Consider approaches such as checksum comparison, streaming val
Bun.serve default bind address: restricting a dev server to localhost only
I'm configuring a development server with Bun.serve() and want to make sure it is never reachable from other machines on the network. My understanding is that when no hostname is given, Bun binds to all interfaces ( 0.0.0.0 / :: ), which would expose the port beyond localhost if the host firewall permits it. My constraints: I want the restriction expressed i
Bun's --hot Reloader and the ESM Module Registry: Which Imports Get Invalidated?
Bun exposes two overlapping mechanisms for loading application code: its transpiling module loader, which caches compiled output so repeat imports are faster, and its watch/hot reload modes ( bun --watch , bun --hot ), which re-execute or patch modules when files on disk change. The boundary between these two mechanisms is not fully specified. In Bun 1.x, ho
Bun Fetch API and Node.js http Module Interoperability
Runtime Request Handling Bun provides a native implementation of the Web Standard Fetch API alongside a compatibility layer for the Node.js http and https modules. While these coexist to support legacy migration, they utilize different underlying mechanisms for request execution and header management. Specification Consistency When migrating from Node.js-sty
Bun test runner and promise rejections: should unhandled async errors fail the test?
Context I'm designing a test suite that relies on Bun's built-in test runner, using its Jest-style glob discovery for .test.ts files alongside source code. Some tests intentionally exercise asynchronous code paths where promises may reject outside an explicit await or try/catch . Uncertainty The documented behavior for unhandled promise rejections inside tes
Investigating Potential Memory Leaks in Bun's Zero‑Copy HTTP Server
Goal: determine whether Bun's zero‑copy HTTP server reuses buffers in a way that can cause memory leaks under sustained high concurrency. Constraints: use the latest stable Bun release, run a simple Bun.serve() endpoint that echoes request bodies, no custom buffer pools, on a Linux system with default TCP stack. Monitor RSS via top or htop while generating t