# bun Published articles for bun. 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 ## Running the WorkOS API locally DevFeed: [Running the WorkOS API locally]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-17T20:30:39Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [API](), [Testing](), [Development](), [servers](), [SDKs](), [OpenAPI Specification](), [Authentication](), [Open Source]() Tags: [api](), [authentication](), [automated](), [backend](), [bun](), [docker](), [javascript](), [linux](), [local](), [macos](), [npm](), [open-source](), [openapi](), [python](), [tests](), [windows]() ### AI overview This tutorial introduces WorkOS Emulate, an open-source local WorkOS API server for development and automated testing. It explains how to run it locally or in CI, connect WorkOS SDKs by overriding the base URL, and use seeded data for repeatable authentication and integration tests without contacting a live WorkOS environment. ### Source excerpt WorkOS Emulate runs the WorkOS API on your own machine, so your tests can seed real data, drive full login flows, and force failures without touching prod. ## Implementing Page Objects in Playwright DevFeed: [Implementing Page Objects in Playwright]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-16T22:04:38Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [Playwright](), [selectors](), [test](), [Development]() Tags: [bun](), [bun-create-playwright](), [code](), [gitlab](), [jest](), [page-object](), [playwright](), [selectors](), [test](), [tests]() ### AI overview A tutorial on using Playwright page objects to organize web application tests, centralize selectors, reduce repetition, and simplify maintenance. It compares Playwright Test and Library approaches and demonstrates setting up a login-page object. ### Source excerpt Picture a login screen, such as The-Internet / Login. On this LoginPage, there is: a heading: Login Page a user name textbox with the label, "Username" a password textbox with the label, "Password" a login button, with the role of a button, and the name of "Login" a flash message that appears if you enter invalid credentials such as "NotAUser" and "NotAPassword". If you successfully log in with "tomsmith" and "SuperSecretPassword!, there is a SecureArea: a heading: "Secure Area" a flash message "You logged into a secure area!" a Logout button. Sure, you could interact with each web element in your test... but what if the username text box locator changes? You would have to update multiple tests every time the element changed. ... Instead, you could place it in a Page Object, something that Playwright handles well! "A page object represents a part of your web application. An e-commerce web application might have a home page, a listings page and a checkout page. Each of them can be represented by page object models. "Page objects simplify authoring by creating a higher-level API which suits your application and simplify maintenance by capturing element selectors in one place and create reusable code to avoid repetition". Using Playwright's Built-In Test Runner? Or Something Else? You may have noticed in https://playwright.dev/docs/pom that there are two different styles of page objects. One for "Test". One for "Library". Test: If you are writing actual Playwright test suites, and Playwright's built in test runner, use the Test section as a guide when creating page objects. Library: If you are integrating Playwright into an existing test framework such as Jest or Cucumber and just want browser automation, instead of having pre-built page fixtures, etc, you can use this format. Setting Up Page Objects Let's review a page object I created for the main login page on my GitLab account for the bun-create-typescript project, tests/pages/LoginPage.ts. The first thing we do is ## How Playwright Frameworks get configured with playwright.config.ts DevFeed: [How Playwright Frameworks get configured with playwright.config.ts]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-15T02:30:20Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [Playwright](), [Testing](), [CI/CD](), [browsers](), [Framework]() Tags: [browsers](), [bun](), [bun-create-playwright](), [ci-cd](), [config](), [playwright](), [testing]() ### AI overview This tutorial examines the playwright.config.ts file generated by `bun create playwright`. It explains default test settings, browser projects for Chromium, Firefox, and WebKit, mobile and branded browser configurations, and how retries differ between local runs and CI/CD pipelines. ### Source excerpt When we installed bun, a new package manager owned by Anthropic, then ran "bun create playwright", a new automation framework was stood up, along with sample tests, and a Playwright configuration file. In this post, we will be examining the file generated: playwright.config.ts. Personally, I find the pre-generated file very hard to scan... there are so many options and documentation in the comments, it is difficult for me to focus on the code. Let's examine just the code generated below. If you need to see the whole file, you can see it here: https://playwright.dev/docs/test-configuration Playwright.dev / Configuration mentions, "Playwright has many options to configure how your tests are run. You can specify these options in the configuration file". What is Configured By Default? import { defineConfig, devices } from '@playwright/test'; export default defineConfig({ testDir: './tests', fullyParallel: true, forbidOnly: !!process.env.CI, retries: process.env.CI ? 2 : 0, workers: process.env.CI ? 1 : undefined, reporter: 'html', // baseURL: 'http://localhost:3000', /* Collect trace when retrying the failed test. See https://playwright.dev/docs/trace-viewer */ trace: 'on-first-retry', }, /* Configure projects for major browsers */ projects: [ { name: 'chromium', use: { ...devices['Desktop Chrome'] }, }, { name: 'firefox', use: { ...devices['Desktop Firefox'] }, }, { name: 'webkit', use: { ...devices['Desktop Safari'] }, }, }); I know what you are thinking ... What the heck is process.env.CI ? 2 : 0? This is know as a ternary operator. It is a shorthand for: "If A then B, else C". You can run tests two ways: Locally, on your local machine, or through a CI / CD Pipeline like Jenkins, GitHub Actions, or GitLab. If you are running tests on CI / CD, the process.env.CI would automatically get set. Since A is true, the value of retries would be "2". If you are running tests locally, the process.env.CI would NOT get set. Since A is false, the value "0" would be selected. CI / ## Checking code with lint, formatting it with prettier DevFeed: [Checking code with lint, formatting it with prettier]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-10T23:23:45Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [ESLint](), [Prettier](), [Playwright](), [Programming]() Tags: [bun](), [bun-create-playwright](), [eslint](), [formatting](), [linter](), [playwright](), [typescript]() ### AI overview This tutorial explains how to add ESLint for static analysis and Prettier for consistent code formatting in a Playwright project. It also discusses eslint-plugin-playwright and using eslint-config-prettier to reduce conflicts between ESLint and Prettier. ### Source excerpt Now that we've installed bun, Anthropic's package manager, scaffolded a Playwright framework and closely examined the results, and added typechecking with TypeScript's compiler, it's time to add ways to check the code with lint, and reformat the code with prettier. We will be using: ESLint, as the static-analysis tool to review the code without running it. Little bits of fluff -- like syntax errors, structural bugs, anti-patterns, and code style violations -- can collect on your code, so it helps to run a linter to help catch it all, such as ESLint. There is also a linter, eslint-plugin-playwright, for Playwright tests. Prettier enforces a consistent code style across your entire codebase. Because ESLint and Prettier can conflict, we will be using Prettier's eslint-config-prettier, which turns off all rules that are unnecessary or might conflict with ESLint. What is a Linter? According to the Wikiwand entry for Lint, "Stephen C. Johnson, a computer scientist at Bell Labs, came up with the term 'lint' in 1978 while debugging the yacc grammar he was writing for C and dealing with portability issues stemming from porting Unix to a 32-bit machine. The term was borrowed from lint, the tiny bits of fiber and fluff shed by clothing, as the command he wrote would act like a lint trap in a clothes dryer, capturing waste fibers while leaving whole fabrics intact. The lint program was released outside of Bell Labs in Unix V7, in 1979. "In his 1978 paper, Johnson explained his reasons for creating a new program to detect errors: '...the general notion of having two programs is a good one' because they concentrate on different things, thereby allowing the programmer to 'concentrate at one stage of the programming process solely on the algorithms, data structures, and correctness of the program, and then later retrofit, with the aid of lint, the desirable properties of universality and portability' " What is ESLint? Website: https://eslint.org/ GitHub: https://github.com/eslint/e ## 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. ## Fixing JavaScript observability, one library at a time DevFeed: [Fixing JavaScript observability, one library at a time]() Original publisher: [Read original article]() Author: Abdelrahman Awad Published: 2026-05-07T00:00:00Z Content type: opinion Language: en Sources: [Sentry Blog]() Topics: [observability](), [JavaScript](), [tracing](), [Instrumentation](), [Node.js](), [OpenTelemetry]() Tags: [bun](), [instrumentation](), [javascript](), [node-js](), [observability](), [opentelemetry](), [tracing]() ### AI overview Sentry describes an effort to replace monkey-patching in server-side JavaScript APM tools with Node's TracingChannel API. The approach lets libraries publish structured events that observability tools can consume without patching, loader hooks, or strict initialization ordering, with stated support across Node, Bun, and Deno. ### Source excerpt Sentry is adding TracingChannel support to 44 JavaScript libraries upstream, replacing fragile monkey-patching with native observability that works across all runtimes. ## Chainguard artifacts safe from npm supply chain attack targeting SAP developer dependencies with 2.25M+ monthly downloads DevFeed: [Chainguard artifacts safe from npm supply chain attack targeting SAP developer dependencies with 2.25M+ monthly downloads]() Original publisher: [Read original article]() Published: 2026-04-29T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Security](), [npm](), [npm packages](), [chainguard](), [GitHub](), [container images](), [Bun](), [Node.js]() Tags: [bun](), [chainguard-containers](), [chainguard-libraries](), [github](), [malicious-packages](), [mini-shai-hulud](), [node-js](), [npm](), [npm-malware](), [npm-worm](), [sap](), [security](), [shai-hulud](), [supply-chain](), [tokens]() ### AI overview A Shai-Hulud-style npm supply-chain attack compromised four SAP Cloud Application Programming Model dependencies with more than 2.25 million combined monthly downloads. The malicious packages used a preinstall hook to download Bun and harvest GitHub tokens, npm tokens, and other developer secrets. Chainguard customers were protected because Chainguard Libraries for JavaScript does not build or serve packages containing install-time scripts, and Chainguard Factory terminated rebuilds when it detected the hook. ### Source excerpt New npm worm targets 2.25M-download packages. Chainguard customers stayed protected by blocking install-time scripts and malicious dependencies. ## 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? ## 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... ## @neondatabase/serverless hits 1.0.0 DevFeed: [@neondatabase/serverless hits 1.0.0]() Original publisher: [Read original article]() Author: George MacKerron Published: 2025-03-25T18:41:48Z Content type: release Language: en Sources: [Blog -- Neon Docs]() Topics: [Serverless](), [JavaScript](), [TypeScript](), [SQL](), [WebSocket](), [Security](), [V8](), [Bun](), [Cloudflare Workers](), [Deno](), [Chrome](), [Firefox]() Tags: [bun](), [chrome](), [cloudflare-workers](), [company](), [drizzle](), [engineering](), [firefox](), [http](), [javascript](), [prisma](), [security](), [serverless](), [sql](), [typescript](), [workers]() ### AI overview Neon's serverless driver for JavaScript and TypeScript reaches version 1.0.0. The release refactors the codebase, automates TypeScript type bundling, adds CI coverage across several runtimes and platforms, and supports Prisma and Drizzle adapters. It also introduces composable tagged-template SQL queries over HTTP and includes security-related changes. ### Source excerpt Neon's serverless driver for JavaScript and TypeScript carries SQL queries over HTTP and WebSockets. It's designed for use in environments where raw TCP connections aren't available and/or low connection latencies are important. That includes V8 isolate-based serverless functions... ## A New Nx Experience for TypeScript Monorepos and Beyond DevFeed: [A New Nx Experience for TypeScript Monorepos and Beyond]() Original publisher: [Read original article]() Author: Juri Strumpflohner Published: 2025-01-29T00:00:00Z Content type: release Language: en Sources: [Juri Strumpflohner]() Topics: [TypeScript](), [Developer experience](), [Package manager]() Tags: [bun](), [developer-experience](), [monorepo](), [monorepo-tools](), [npm](), [npm-workspaces](), [nx](), [pnpm](), [release](), [tooling](), [typescript]() ### AI overview Nx introduces a workspaces-based setup that combines NPM, Yarn, PNPM, or Bun workspaces with TypeScript project references for monorepos. The article explains the expected performance, memory-use, and editor-support benefits, while noting that the feature is initially behind a flag. ### Source excerpt Discover how Nx's new workspaces setup combines package managers with TypeScript project references for better performance and developer experience in monorepos. ## Docusaurus 3.7 DevFeed: [Docusaurus 3.7]() Original publisher: [Read original article]() Author: Sébastien Lorber Published: 2025-01-03T00:00:00Z Content type: release Language: en Sources: [Docusaurus Blog]() Topics: [React](), [changelog](), [upgrade](), [SVG](), [Algolia](), [Bun]() Tags: [algolia](), [bun](), [changes](), [react](), [release](), [svg](), [upgrade](), [version]() ### AI overview Docusaurus 3.7 adds React 19 support, makes React 19 the default for newly initialized sites, and retains React 18 support for existing sites. The release also adds configurable SVGR options and includes other updates to integrations, performance, and translations. ### Source excerpt We are happy to announce Docusaurus 3.7. ## 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. [Next page]()