# Bun Bun is an all-in-one JavaScript runtime and toolkit with an integrated package manager, test runner, and bundler. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Bun runtime now supports large functions and extended max duration DevFeed: [Bun runtime now supports large functions and extended max duration]() Original publisher: [Read original article]() Author: Florentin Eckl Published: 2026-08-24T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Bun](), [Vercel](), [Node.js](), [Python]() Tags: [2026](), [bun](), [compute](), [enterprise](), [features](), [node-js](), [python](), [vercel]() ### AI overview Vercel Functions now supports larger package sizes and longer execution times for the Bun runtime. In beta, Fluid compute enables packages up to 5GB uncompressed and function durations up to 30 minutes for Pro and Enterprise teams. ### Source excerpt The Bun runtime on Vercel Functions now supports larger package sizes up to 5GB uncompressed and extended max duration for up to 30 minutes, two betas that previously ran on Node.js and Python only. Large functions raise the standard 250MB package size limit to 5GB, and extended max duration raises the generally available 800-second ceiling to 1800 seconds for Pro and Enterprise teams. Both features require Fluid compute to be enabled. New projects are enrolled in the large functions beta automatically, while existing projects created before July 2026 opt in by adding VERCEL_SUPPORT_LARGE_FUNCTIONS=1 as an environment variable in your project settings, then redeploying. Durations above 800 seconds are set per function in vercel.json rather than as a project-level default: The server.ts entry point serves the long-running route with Bun: During the beta, these features are unavailable on projects using Secure Compute or Static IPs. Read the large functions and extended max duration documentation. Read more ## Bun 1.4 lands on Appwrite: the first Bun written in Rust DevFeed: [Bun 1.4 lands on Appwrite: the first Bun written in Rust]() Original publisher: [Read original article]() Author: Atharva Deosthale Published: 2026-08-21T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Bun](), [Appwrite](), [Rust](), [OpenTelemetry](), [Playwright]() Tags: [announcements](), [build](), [bun](), [node](), [npm](), [opentelemetry](), [playwright](), [release](), [rust]() ### AI overview Bun 1.4 is available on Appwrite Cloud for Appwrite Functions and Sites. The release is the first Bun version written in Rust and includes improved Node.js 26 compatibility, faster startup and installs, lower memory and idle CPU use, native Web Streams, and new built-in APIs. The article also describes upgrade considerations and benchmarks against Bun 1.3 and Node 26. ### Source excerpt Bun 1.4 is now available as a runtime for Appwrite Functions and as a build runtime for Appwrite Sites. We benchmarked it against Bun 1.3 and Node 26. ## How to Configure Playwright Test to run smoke tests, headed tests, and debug versions through scripts in package.json DevFeed: [How to Configure Playwright Test to run smoke tests, headed tests, and debug versions through scripts in package.json]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-20T02:13:32Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [Playwright](), [Script](), [Bun](), [Smoke Tests](), [test](), [Package manager]() Tags: [bun](), [bun-create-playwright](), [commands](), [gitlab](), [how-to](), [install](), [playwright](), [test](), [tests]() ### AI overview A tutorial on configuring Playwright Test commands in package.json scripts. It demonstrates shortcuts for headed, traced, Chromium, Firefox, WebKit, smoke, debugging, reporting, linting, formatting, and type-checking workflows, and explains using Bun and bunx to run commands. ### Source excerpt Earlier, we went over how we could create scripts in the package.json file of our Playwright framework to add typechecking, linting, and formatting your code with prettier. Want to see the entire bun-create-playwright project? It is on tinyurl.com/bun-create-playwright! With this post, we will explore how the built-in test runner for Playwright Test can run headed tests, debug versions of tests, and smoke tests. ... and shortcuts for all of these can be set up in the scripts in your package.json! If you are using "bun" as a package manager, as we are in bun-create-playwright, just type out "bun run", a space and then the shortcut such as: bun run test package.json "scripts": { "test": "playwright test", "test:headed": "playwright test --headed", "test:trace": "playwright test --trace on", "test:chromium": "playwright test --project=chromium", "test:firefox": "playwright test --project=firefox", "test:webkit": "playwright test --project=webkit", "test:smoke": "playwright test --project=chromium --grep '@smoke'", "test:flaky": "playwright test --project=chromium --repeat-each=20", "test:ui": "playwright test --ui", "test:debug": "playwright test --debug", "test:failed": "playwright test --last-failed", "test:login": "playwright test tests/login.spec.ts", "test:secure-area": "playwright test tests/secure-area.spec.ts", "report:list": "playwright test --reporter=list", "report:line": "playwright test --reporter=line", "report:dot": "playwright test --reporter=dot", "report:blob": "playwright test --reporter=blob", "report": "playwright show-report", "codegen": "playwright codegen", "lint": "eslint .", "lint:ci": "eslint . --max-warnings 0", "lint:fix": "eslint . --fix", "format": "prettier --write .", "format:check": "prettier --check .", "format:debug": "prettier --check . --log-level debug", "format:diff": "prettier --list-different", "typecheck": "tsc --noEmit" }, bun-create-playwright / package.json Do you need to really set up shortcuts like these? Certainly not! B ## Bun 1.4 is now available in Vercel Functions DevFeed: [Bun 1.4 is now available in Vercel Functions]() Original publisher: [Read original article]() Author: Tom Lienard Published: 2026-08-20T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Bun](), [Vercel](), [Rust](), [Node.js](), [WebSocket](), [Zig](), [Hono](), [Next.js]() Tags: [2](), [bun](), [compatibility](), [compute](), [cpu](), [features](), [frameworks](), [next-js](), [node](), [node-js](), [performance](), [release](), [rust](), [support](), [update](), [vercel](), [zig]() ### AI overview Vercel Functions now support Bun 1.4, which rewrites Bun from Zig to Rust and includes resolved issues, additional Node.js compatibility tests, new features, and performance improvements. Bun runs on Fluid compute, supports Active CPU pricing and WebSockets, and works with frameworks including Next.js and Hono. Upgrading is an explicit opt-in because of breaking changes. ### Source excerpt Vercel Functions now support the new Bun 1.4 release, a rewrite of Bun from Zig to Rust, with over 2,900 issues resolved, more than 1,500 additional Node.js compatibility tests passing, and new features and performance improvements. Bun on Vercel Functions: Runs on Fluid compute with Active CPU pricing Supports WebSockets and Bun.serve() Supports common frameworks such as Next.js, Elysia, and Hono To update from the previous Bun version, set bunVersion to 1.4.x in vercel.json. Upgrading is an explicit opt-in because Bun 1.4 has several breaking changes. Review the breaking changes and update your application before upgrading. Learn more about using Bun on Vercel in the runtime documentation. Read more ## Bun runtime for Vercel Functions now accepts Bun.serve as an entrypoint DevFeed: [Bun runtime for Vercel Functions now accepts Bun.serve as an entrypoint]() Original publisher: [Read original article]() Author: Florentin Eckl Published: 2026-08-10T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Bun](), [Vercel](), [WebSocket](), [servers]() Tags: [bun](), [compute](), [concurrent](), [data](), [external](), [pricing](), [server](), [vercel]() ### AI overview Vercel Functions now support Bun.serve() as a Bun runtime entrypoint, including WebSocket handlers. Locally run Bun servers can deploy as-is without being wrapped in a framework, with routes defined in a project-level server.ts file. ### Source excerpt The Bun runtime for Vercel Functions now supports Bun.serve() as a function entrypoint, including WebSocket handlers. The server you run locally with Bun deploys as-is, without being wrapped in a framework. Enable the runtime by setting "bunVersion": "1.x" in vercel.json. Deploy a routes-based server Create a server with a routes map in server.ts at the project root. Accept WebSocket connections Add a websocket handler and call server.upgrade(request) in fetch to upgrade matching requests. The rest of the server stays the same. WebSocket connections run on Fluid compute with Active CPU pricing, so you pay only for time spent processing messages, not idle connection time. A connection is pinned to one function instance for its lifetime, and a single instance can handle multiple concurrent connections. Use an external data store to coordinate messages across instances. Read the documentation to get started. Read more ## Add Type Checking and TSConfig to Bun-Create-Playwright DevFeed: [Add Type Checking and TSConfig to Bun-Create-Playwright]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-08T03:10:43Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [Bun](), [TypeScript](), [Playwright](), [Compiler](), [Code](), [Command-line interface]() Tags: [bun](), [bun-create-playwright](), [code](), [compiler](), [playwright](), [terminal](), [typescript]() ### AI overview This tutorial adds TypeScript type checking and tsconfig configuration to a Bun-Create-Playwright project. It explains why Playwright should be run alongside the TypeScript compiler and demonstrates using tsc --noEmit to check code without emitting output files. ### Source excerpt Now that we have installed bun, Anthropic's package manager, and scaffolded a Playwright framework and closely examined the results, we are going to explore with our Bun-Create-Playwright project ways to check if our code is correct. The first method we will be exploring is typechecking. Why Typechecking? As the Playwright.dev / Node.js Introduction mentions: "[...] Playwright does not check the types and will run tests even if there are non-critical TypeScript compilation errors. We recommend you run TypeScript compiler alongside Playwright. "[...] Note that Playwright only supports the following tsconfig options: allowJs, baseUrl, paths, references and extends. "[...] By default, Playwright will look up a closest tsconfig for each imported file by going up the directory structure and looking for tsconfig.json or jsconfig.json. This way, you can create a tests/tsconfig.json file that will be used only for your tests and Playwright will pick it up automatically".Before we go further down this road... What is Type Checking? According to Type Checking in TypeScript: A Beginners Guide, every piece of data in TypeScript is given a "type", and this "type" determines what properties the data has, and what methods are available to it. The types can be things like a Number, String, Enum, Boolean, Array, Object, Type assertions, or others. Since all data in TypeScript is given a type, it means that the TypeScript compiler, tsc, can check every property to make sure it is being used correctly. It makes sure that the expected properties exist and that the methods and functions are all compatible. And best of all, you can run these checks in your IDE as you are writing the code! To run typechecking against our code, all we have to do is execute from the Terminal: tsc --noEmit Since we are just kicking the tires of our code to see what happens, we don't need to emit "compiler output files like JavaScript source code, source-maps or declarations. This makes room for another tool ## Scaffold and Run Playwright Tests with Bun DevFeed: [Scaffold and Run Playwright Tests with Bun]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-06T17:37:06Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [Playwright](), [Bun](), [Node.js](), [TypeScript](), [Windows]() Tags: [bun](), [bun-create-playwright](), [playwright](), [test](), [typescript](), [windows]() ### AI overview A tutorial on creating a TypeScript Playwright project with Bun, installing its browsers on Windows, configuring a Bun lockfile and test script, and running the included tests. It notes that Playwright's test runner remains a Node.js program and documents an additional Bun and Playwright installation step for a Windows bug. ### Source excerpt We covered in the last blog post how to install bun, a new package manager. In this blog post, we will look into using bun to install a new Playwright framework. Create the Playwright Framework Once I installed bun on my Windows PC and was up and running I created a new folder, "bun-create-playwright". I opened up that folder in VS Code, along with a new PowerShell terminal. In that terminal I entered: bun create playwright This activated the interactive Playwright installer that Playwright comes with. I selected I wanted it to create for me a TypeScript project, placing the tests in the default folder, tests, but I decided not to add a GitHub Actions workflow. I wanted to experiment with using GitLab. I chose it to set up and install all the browsers for me... which it did... using NPX, part of Node. Wait a second, when it comes to our Playwright framework, doesn't bun replace node? No. Bun might be a JavaScript runtime, a package manager, and a bundler shipped as a single software tool, but in our case we are simply using it as a package manager in our Playwright framework. Bun works alongside Node.js in the Playwright project. We still use Playwright's test runner, a Node.js program. Bun handles installations and run tasks. Alert: Windows Bug! Initially, that wasn't enough to install Playwright's internal browsers. There is a bug with bun + Playwright Windows where we also need to: bun add --dev @playwright/test bunx playwright install That was enough for the browsers to install. Create the Bun Lock File After the browsers are installed, we need to install bun in our project, to create from the package.json a bun installation. Run in the Terminal: bun install Review the newly created file bun.lock.file in the root directory of the project. Delete the package-lock.json file. Add the test script to the Package.json If you look in the package.json file, you can see that the scripts code block is currently empty. "scripts": {} Inside this code block, we will be addin ## Introducing bun, a new package manager and JavaScript runtime environment DevFeed: [Introducing bun, a new package manager and JavaScript runtime environment]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-06T01:58:25Z Content type: article Language: en Sources: [T.J. Maher]() Topics: [Bun](), [Package manager](), [JavaScript](), [Playwright](), [Node.js]() Tags: [bun](), [bun-create-playwright](), [getting-started](), [installation](), [javascript](), [node-js](), [playwright](), [test-automation](), [typescript]() ### AI overview This article examines Bun as a JavaScript package manager and runtime, including its use with Playwright projects. It explains how Bun compares with npm, Yarn, and pnpm, and discusses its integrated tooling and claimed performance advantages. ### Source excerpt New job? New toolset to explore! In this post I'll be investigating a new JavaScript package manager and runtime environment called bun.sh. You may have noticed on Playwright.Dev's Getting Started / Installation section there are three different ways to install a ui or api test automation framework with the latest version of Playwright: npm init playwright@latest yarn create playwright pnpm create playwright For this blog post I'll be investigating a fourth way, the new toolset they just started using at work, bun.sh. bun create playwright What is npm, yarn, pnpm, and bun? These are called package managers. What is a package? Developing a project, you don't have to figure out how to code everything yourself. You can include in your projects outside libraries, or "packages" of code from from the public JavaScript registry npmjs.com. The problem is that these packages then need to be downloaded, installed, managed, and updated whenever they are updated. JavaScript projects can use a package manager, such as bun, to help this process. When putting together a Playwright automation framework based around JavaScript and TypeScript, Playwright uses the Node.js JavaScript runtime environment, to run its test runner, execute automation scripts, and manage its browser instances.(See Nodejs.org / About ) There is a division of labor: Node.js runs these internal functions like running tests. NPM, Yarn, PNPM, and now Bun handle the packages. Why are there so many package managers? Each has its own specialization. The original NPM is bundled already with Node.js. Yarn is a Facebook toolset that was created when NPM was found to work too slow. PNPM was created to be smaller and therefore faster. And bun was built for quick startup and installation speed, good especially if you have a CI/ CD pipeline that has a LOT of packages to install each time the tests run. NPM, released in 2010, is the Node Package Manager for Node.js, a JavaScript Runtime Environment. According to NodeJS.org ## Bun's migration from Zig to Rust reduced the estimated timeline from 1-2 years to 11 days DevFeed: [Bun's migration from Zig to Rust reduced the estimated timeline from 1-2 years to 11 days]() Original publisher: [Read original article]() Author: Ivan Klaric Published: 2026-07-16T16:50:20Z Content type: opinion Language: en Sources: [The Pragmatic Engineer]() Topics: [Bun](), [migration](), [Rust](), [Zig](), [Fable](), [Memory Leaks]() Tags: [bun](), [fable](), [memory-leaks](), [migration](), [rust](), [zig]() ### AI overview The article examines Bun's rewrite from Zig to Rust, focusing on memory-safety problems and the migration approach. It reports that the migration timeline was shortened from an estimated 1-2 years to 11 days, while emphasizing that thorough testing was required. ### Source excerpt To a sceptic, spending $165K to migrate Bun from Zig to Rust sounds very expensive. But to a realist, shortening a 1-2 year migration down to 11 days opens amazing new opportunities for devs. However, a thoroughly-tested project is required to pull it off. ## Mini Shai-Hulud Hits AntV: 300+ Malicious npm Packages Published via Compromised Maintainer Account DevFeed: [Mini Shai-Hulud Hits AntV: 300+ Malicious npm Packages Published via Compromised Maintainer Account]() Original publisher: [Read original article]() Author: Liran Tal Published: 2026-05-18T23:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Data visualization](), [npm packages](), [Malware](), [npm](), [C2](), [Bun](), [JavaScript](), [GitHub]() Tags: [awareness](), [blog](), [c2](), [data-visualization](), [developer](), [devops](), [devrel](), [javascript](), [malware](), [npm-packages](), [payload](), [secrets](), [security](), [snyk-open-source](), [snyk-platform](), [supply-chain](), [supply-chain-security](), [teampcp](), [tokens]() ### AI overview This article analyzes the Mini Shai-Hulud supply-chain attack targeting the AntV data visualization ecosystem through a compromised npm maintainer account. It describes the mass publication of malicious package versions, the embedded Bun payload, credential and secret theft, C2 persistence, and self-propagation using stolen npm tokens. ### Source excerpt A compromised npm maintainer account triggered an automated burst of over 300 malicious package versions across 323 packages in the AntV data visualization ecosystem, part of the ongoing Mini Shai-Hulud supply chain worm campaign. Here's what the malware does, how to detect exposure, and how to respond. ## Shai-Hulud Goes Open Source DevFeed: [Shai-Hulud Goes Open Source]() Original publisher: [Read original article]() Author: Ryan Simon, Sebastian Obregoso, Greg Foss Published: 2026-05-13T00:00:00Z Content type: article Language: en Sources: [Datadog Security Labs]() Topics: [Open Source](), [Code](), [TypeScript](), [Bun](), [JavaScript](), [CI/CD](), [Cloud](), [Persistence](), [Linux](), [macOS](), [AI Agent](), [ssh]() Tags: [analysis](), [attacks](), [c2](), [ci-cd](), [cloud](), [code](), [framework](), [github](), [javascript](), [kubernetes](), [linux](), [macos](), [open-source](), [persistence](), [ssh](), [supply-chain](), [teampcp](), [typescript]() ### AI overview A static analysis of the Shai-Hulud offensive framework attributed to TeamPCP. The article examines its TypeScript/Bun architecture, credential harvesting, supply-chain poisoning, CI/CD targeting, persistence, and encrypted data exfiltration. ### Source excerpt A static analysis of the open-sourced Shai-Hulud offensive framework attributed to TeamPCP, covering its credential harvesting, supply chain poisoning, and exfiltration capabilities. ## Introducing @supabase/server DevFeed: [Introducing @supabase/server]() Original publisher: [Read original article]() Author: Tomás Pozo; Kalleby Santos; Katerina Skroumpelou; Matt Johnston Published: 2026-05-06T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Authentication](), [JSON Web Tokens](), [Boilerplate](), [Workers](), [Bun](), [Hono]() Tags: [auth](), [authentication](), [cloudflare-workers](), [code](), [post](), [security](), [workers]() ### AI overview Supabase introduces @supabase/server in public beta, a package that provides authentication verification, Supabase client setup, request context, CORS handling, and common server-side helpers across Edge Functions, Vercel Functions, Cloudflare Workers, Hono, and Bun. It supplies user-scoped and admin clients, verified identity, and JWT claims while reducing repeated setup code. ### Source excerpt Stateless auth, RLS-scoped clients, and CORS on the server, without the boilerplate. ## lightning PyPI Compromise: A Bun-Based Credential Stealer in Python DevFeed: [lightning PyPI Compromise: A Bun-Based Credential Stealer in Python]() Original publisher: [Read original article]() Author: Stephen Thoemmes Published: 2026-04-30T00:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Security](), [Malware](), [Python](), [Bun](), [JavaScript](), [GitHub](), [snyk-learn](), [npm](), [releases]() Tags: [article](), [awareness](), [ci-cd](), [code](), [developer](), [devops](), [github](), [javascript](), [open-source-security](), [payload](), [python](), [release](), [sbom](), [secrets](), [security](), [security-labs](), [snyk-learn](), [snyk-open-source](), [snyk-security-intel](), [supply-chain-security](), [tech](), [vulnerability-insights]() ### AI overview A compromised lightning PyPI release downloads the Bun JavaScript runtime at import time and executes an approximately 11 MB obfuscated credential stealer. The article covers the package compromise, Snyk advisory, remediation, and similarities to the preceding Mini Shai-Hulud npm campaign. ### Source excerpt A malicious release of the lightning PyPI package ships a credential-stealing Bun payload that runs on import. Snyk has a live advisory. Here's what's in the package, what to rotate, and how the payload pattern connects to the Mini Shai-Hulud npm campaign one day earlier. ## How fast do browsers correct UTF-16 strings? DevFeed: [How fast do browsers correct UTF-16 strings?]() Original publisher: [Read original article]() Author: Daniel Lemire Published: 2026-02-21T20:07:17Z Content type: article Language: en Sources: [Daniel Lemire]() Topics: [JavaScript](), [Benchmark](), [Chrome](), [Chromium](), [Edge](), [Bun]() Tags: [benchmark](), [browsers](), [bun](), [chrome](), [chromium](), [edge](), [javascript](), [programming]() ### AI overview This article explains how JavaScript represents UTF-16 strings, how invalid surrogate sequences can be repaired with toWellFormed, and how fast the operation runs. A benchmark across browsers and JavaScript runtimes found varied performance; Chromium-based browsers exceeded ten gigabytes per second in the reported test. ### Source excerpt JavaScript represents strings using Unicode, like most programming languages today. Each character in a JavaScript string is stored using one or two 16-bit words. The following JavaScript code might surprise some programmers because a single character becomes two 16-bit words. > t="🧰" '🧰' > t.length 2 > t[0] '\ud83e' > t[1] '\uddf0' The convention is ... Continue reading How fast do browsers correct UTF-16 strings? ## Laravel December Product Releases DevFeed: [Laravel December Product Releases]() Original publisher: [Read original article]() Author: Laravel Team Published: 2026-01-09T12:09:21Z Content type: release Language: en Sources: [Laravel Blog]() Topics: [Laravel](), [releases](), [Cloud](), [Deployment](), [debugging](), [Tooling](), [Bun](), [npm](), [Yarn](), [PHP]() Tags: [billing](), [cloud](), [code](), [debugging](), [deployment](), [javascript](), [laravel](), [markdown](), [product](), [releases](), [tooling](), [updates]() ### AI overview Laravel's December product releases add billing alerts for Laravel Cloud, more flexible deployment workflows in Forge, Markdown-based exception sharing in Nightwatch, and framework improvements to HTTP clients, promises, service reloading, lazy objects, and email templates. ### Source excerpt See what you can do with our latest product releases: set up billing alerts in Laravel Cloud, and ship faster with framework, Forge, and Nightwatch updates. ## DigitalOcean App Platform Adds Native Bun Support DevFeed: [DigitalOcean App Platform Adds Native Bun Support]() Original publisher: [Read original article]() Author: Dinesh Murthy Published: 2025-12-19T03:17:43Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [Bun](), [Digital Ocean](), [Deployment](), [JavaScript](), [Node.js](), [Next.js]() Tags: [bun](), [cloud](), [deployment](), [digitalocean](), [javascript](), [next-js](), [node-js](), [platform](), [serverless]() ### AI overview DigitalOcean App Platform now supports deploying Bun applications directly from a code repository. Its Cloud Native Buildpacks detect, build, deploy, and run Bun applications without requiring configuration or a Dockerfile. ### Source excerpt The JavaScript ecosystem is rapidly evolving to meet the growing performance and integration demands of modern, AI-driven applications. Bun is a popular framework for developers that offers an all-in-one runtime, bundler, and package manager and is considered a drop-in replacement for Node.js. With its faster startup times and lower memory usage than traditional runtimes, Bun is a top request from our customers. Today, we're excited to announce native Bun support on DigitalOcean App Platform. Now, you can deploy Bun applications directly from your code repository without writing a single line of configuration. App Platform's Cloud Native Buildpacks will automatically detect, build, deploy and run your Bun apps. Benefits Performance: Bun is a modern, high-performance JavaScript runtime with integrated tooling, optimized for fast startup and efficient execution. Zero Configuration: You don't need to maintain a Dockerfile. Just push your code into your git repo, and we'll handle the runtime setup. Seamless Next.js Support: Bun works natively with Next.js, allowing you to deploy your full-stack React applications with the same ease. Deployment Paths in App Platform App Platform supports three distinct workflows as part of deployment. Cloud Native Buildpacks (The "Code-First" Way): You simply connect a GitHub, GitLab, or Bitbucket repository. We analyze your code, detect the language, and build it automatically. Dockerfiles: You include a Dockerfile in your repo. We detect it and build the image according to your instructions. Pre-Built Images: You build the container image locally and push it to the DigitalOcean Container Registry (DOCR). We deploy exactly what you pushed. How to Get Started with Bun If you're new to Bun, getting started is straightforward. Bun is designed to be a drop-in replacement for Node.js, meaning you can often use your existing code and package.json with minimal changes. Install Bun: Fast-track your setup by installing Bun globally on your local ## Zed Productivity Workflows and Hidden Features from the Team and Community DevFeed: [Zed Productivity Workflows and Hidden Features from the Team and Community]() Original publisher: [Read original article]() Author: Joseph Lyons Published: 2025-12-11T00:00:00Z Content type: tutorial Language: en Sources: [Zed Industries - Blog]() Topics: [Bun](), [Command-line interface](), [Terminal](), [Extension]() Tags: [bun](), [community](), [extension](), [productivity](), [terminal](), [tests](), [workflows]() ### AI overview This article presents productivity workflows and hidden Zed features contributed by the team and community. It explains how to customize and rerun tasks, configure Bun test tasks, add file and tab icons, create custom keybindings, and attach terminals to project-specific tmux sessions. ### Source excerpt Favorite workflows and hidden features from the Zed team and community. ## Sharing Excess Uses Neon Database Branches for Development Environments DevFeed: [Sharing Excess Uses Neon Database Branches for Development Environments]() Original publisher: [Read original article]() Author: Taraneh Dohmer Published: 2025-10-23T17:49:17Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Database](), [Drizzle](), [Bun](), [React](), [Vite]() Tags: [bun](), [case-studies](), [database](), [drizzle](), [react](), [vite]() ### AI overview This case study describes how Sharing Excess, a nonprofit food-rescue organization, uses Neon database branches for production, staging, and per-developer environments. Its three-person engineering team uses a Bun and TypeScript monorepo with React, Vite, Hono, Postgres, and Drizzle ORM. ### Source excerpt "For a small team, branching and scale-to-zero just make our lives markedly easier. We're able to use real data without risky scripts touching production, and we don't pay overnight for what we don't use." -- Ryan McHenry, Head of Technology, Sharing Excess What is Sharing Excess?... ## Databuddy Is Open-Sourcing Privacy-First Analytics, Built on Neon DevFeed: [Databuddy Is Open-Sourcing Privacy-First Analytics, Built on Neon]() Original publisher: [Read original article]() Author: Carlota Soto Published: 2025-08-28T15:50:25Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [product analytics](), [Open Source](), [Next.js](), [Tailwind CSS](), [Bun](), [Front end](), [Supabase](), [Back end](), [Prisma]() Tags: [analytics](), [backend](), [bun](), [case-studies](), [frontend](), [next-js](), [open](), [open-source](), [privacy](), [product-analytics](), [self-hosted](), [web]() ### AI overview The article introduces Databuddy, a privacy-first web and product analytics platform that is open source and available through a free plan. It describes the project's preference for a composable stack and explains why its creator chose Neon for serverless Postgres, citing simplicity, performance, and reduced maintenance. The supplied text also identifies a frontend built with Next.js, Tailwind CSS, and Bun, while the API-layer description is truncated. ### Source excerpt "I was surprised by how fast Neon was. It was faster than my self-hosted setup and Prisma Postgres. This plus the convenience of the Free Plan makes it a no-brainer for building your projects." (Issa Nassar, founder of Databuddy) Databuddy is a new privacy-first web and product a... ## New Chainguard Images November 2024: Bun, CockroachDB, Open Liberty DevFeed: [New Chainguard Images November 2024: Bun, CockroachDB, Open Liberty]() Original publisher: [Read original article]() Published: 2024-12-18T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [Bun](), [CockroachDB](), [open liberty]() Tags: [bun](), [chainguard-images](), [cockroachdb](), [container-images](), [open-liberty](), [selenium](), [zero-cves]() ### AI overview Chainguard announces 70 container images built in November 2024, including images for Open Liberty, CockroachDB, and Bun. The article describes the new images and their stated runtime, database, and JavaScript-tooling use cases. ### Source excerpt Check out the new zero-CVE Chainguard Images built in November 2024, including offerings for Bun, CockroachDB, Open Liberty, Selenium, and more. ## Leveraging Bun on Vultr: A superior Node.js alternative DevFeed: [Leveraging Bun on Vultr: A superior Node.js alternative]() Original publisher: [Read original article]() Author: vultr Published: 2024-01-17T00:00:00Z Content type: article Language: en Sources: [MDN Blog]() Topics: [Bun](), [Node.js](), [JavaScript](), [ECMAScript](), [CommonJS](), [Cloud]() Tags: [bun](), [cloud](), [compatibility](), [javascript](), [memory](), [node-js](), [speed]() ### AI overview This guide presents Bun as a fast, all-in-one JavaScript runtime and drop-in replacement for Node.js. It covers Bun's package manager, bundler, test runner, built-in APIs, ECMAScript module and CommonJS compatibility, and Node.js compatibility. It also explains differences between Bun's JavaScriptCore engine and the V8 engine used by Node.js and Deno, then demonstrates running a Bun application on a Vultr Cloud Compute server. ### Source excerpt This guide explains Bun functionalities as a runtime package manager and a bundler. It also explains the benefits of built-in Bun APIs and how to use Bun's Vultr marketplace application. ## 🔥 Bun 1.0, React Server Components, V0.dev DevFeed: [🔥 Bun 1.0, React Server Components, V0.dev]() Original publisher: [Read original article]() Author: Mads Brodt Published: 2023-09-20T15:00:00Z Content type: opinion Language: en Sources: [Front-End Focus]() Topics: [Bun](), [React](), [JavaScript](), [Development]() Tags: [bun](), [dev](), [javascript](), [react]() ### AI overview This newsletter issue discusses Bun 1.0, describing it as a stable JavaScript runtime, package manager, bundler, and test runner focused on performance and developer ergonomics. It also introduces React Server Components and highlights their paradigm shift and learning curve. ### Source excerpt Hey hey,