DEV Community: GXY Gomi

Addfox 0.2.0: Architecture Refactoring & Dependency Slimming

GXY Gomi — Sat, 30 May 2026 13:43:50 +0000

Addfox 0.2.0: Architecture Refactoring & Dependency Slimming

We are excited to share the latest progress on the Addfox framework (https://github.com/addfox/addfox). Version 0.2.0 is now officially released, featuring a significant architecture refactoring. This update focuses on three core goals: reducing dependencies, replacing black-box tools with built-in alternatives, and improving the developer experience for browser extension development.

Dependency Slimming & Supply Chain Security

One of the most impactful changes in this refactoring is the aggressive removal of third-party dependencies that carried large transitive trees. Every external dependency is a potential supply-chain risk—whether through deprecation, malicious takeover, or breaking changes in transitive packages. By replacing large third-party tools with focused, built-in utilities, we have drastically shrunk the attack surface for Addfox users.

Here is what we removed:

web-ext (~586 KB + 26 transitive deps) — completely removed.
chrome-launcher — removed.
archiver (~40 KB + 9 transitive deps) — replaced with a built-in zip alternative.
cli-table3 (~46 KB + 1 transitive dep) — removed from @addfox/core.
chalk (~44 KB), kolorist, minimist — removed from create-addfox-app and replaced with lightweight built-in utilities.

The result? The pnpm-lock.yaml shrank by approximately 2,156 lines, meaning faster installs, smaller node_modules, and fewer supply-chain risks for end users.

Before vs. After: Third-Party Runtime Dependencies

Package	0.1.1 Third-Party Deps	Dev-Launch Third-Party Deps
`@addfox/cli`	`archiver`	(none)
`@addfox/core`	`cli-table3`, `jiti`	`jiti`
`create-addfox-app`	`chalk`, `kolorist`, `minimist`, `prompts`	`prompts`
`@addfox/rsbuild-plugin-extension-hmr`	`chrome-launcher`, `web-ext`	(none)
`@addfox/launcher`	N/A (new package)	(none)
`@addfox/common`	(none)	(none)
`@addfox/pkg-manager`	(none)	(none)
`@addfox/utils`	`@addfox/common`	`@addfox/common`
`rsbuild-plugin-extension-entry`	`@addfox/core`	`@addfox/core`
`rsbuild-plugin-extension-manifest`	`@addfox/core`	`@addfox/core`
`rsbuild-plugin-extension-monitor`	`@addfox/common`, `@addfox/core`	`@addfox/common`, `@addfox/core`

What remains? Only two mature, tiny third-party runtime dependencies:

jiti — a lightweight TypeScript config loader (~50 KB, zero transitive deps).
prompts — a minimal CLI prompt library (~30 KB, zero transitive deps).

Everything else is either internal (@addfox/*) or handled by the build toolchain (@rspack/core as a dev dependency).

Introducing `@addfox/launcher`

Previously, Firefox development relied on web-ext run, a powerful tool with heavy dependencies. We have built @addfox/launcher from the ground up:

Zero runtime dependencies.
Unified support for Chromium (Chrome, Edge, etc.) and Gecko (Firefox, Zen, etc.).
Firefox HMR now uses the RDP protocol to reload temporary add-ons directly, eliminating the need for web-ext's complex process management.
Removed compatibility files such as web-ext.d.ts, web-ext-logger.d.ts, and web-ext-console-stream-hook.ts.

This makes the dev server faster to start, easier to debug, and fully under our control.

HMR Plugin Refactoring

The @addfox/rsbuild-plugin-extension-hmr package saw the largest code reduction:

launcher.ts and runner.ts were heavily simplified after dropping web-ext.
The extension manager now handles profile directories and reload logic more cleanly.
Keyboard reload and WebSocket server paths were streamlined.

Overall, the workspace diff shows roughly 50 files changed, with a net reduction of ~1,641 lines of code—less code to maintain, fewer edge cases, and better reliability.

Enhanced Test Coverage

We did not just delete code; we also invested in quality:

rsbuild-plugin-extension-entry: +260 lines of tests
rsbuild-plugin-extension-hmr: +114 lines of tests
rsbuild-plugin-extension-manifest: +101 lines of tests
rsbuild-plugin-extension-monitor: +112 lines of tests

Official Release

The architecture refactoring and dependency slimming described above are now officially released as version 0.2.0. Upgrade today and thank you for using Addfox!

Addfox: Build Better Browser Extensions for Developers and AI

GXY Gomi — Sun, 22 Mar 2026 16:41:41 +0000

🚀 A new open-source browser extension framework just dropped: Addfox (beta)

👉 https://addfox.dev

👉 github: https://github.com/addfox/addfox

👉 npm: https://www.npmjs.com/package/addfox

If you’ve built extensions recently, you’ve probably used tools like WXT or Plasmo.

They’ve pushed the ecosystem forward a lot — better DX, faster builds, less boilerplate.

But I built something a bit different: Addfox("Addon + Fox"). I want to "Build Better Extensionsfor Developers and AI".

⚡ What is Addfox?

Addfox is a browser extension framework built on top of Rsbuild / Rstack.

⚡ Rust-powered build performance
🧩 More predictable bundling behavior
🧩 Content UI support. Built-in createContentUI method for easy integration of Iframe, ShadowDom, and native content.
🧩 Framework agnostic. Vanilla, Vue, React, Preact, Svelte, Solid — use what you like
🧩 Zip on build. Build automatically outputs an extension zip package
🧩 Enable terminal error output with --debug. Capture all extension errors without browser DevTools, so you can Ask AI directly in any editor
🧩 Skills support for Agents
🧩 llms.txt and markdown metadata support
For more features, please visit the official website

📦 Current status

Beta released
Core workflow is stable
Not supporting Safari right now
Still iterating based on real-world usage

If you’ve ever felt constrained by existing extension frameworks,

or just want something faster and more transparent, give it a try:

👉 https://addfox.dev

Would love to hear how it compares to your current setup.

Supercharge Your Bun Workflow with bun-tasks

GXY Gomi — Sun, 12 Oct 2025 11:35:30 +0000

Supercharge Your Bun Workflow with `bun-tasks`

If you’ve ever wished Bun had a drop-in parallel runner like concurrently, meet bun-tasks—a Bun-first CLI that streamlines multi-command orchestration without leaving the Bun ecosystem.

Why `bun-tasks`?

Bun-native: Designed specifically for the Bun runtime—no Node shims, no compatibility hacks. Just run bun --version to make sure Bun is ready and you’re good to go.
Simple parallelism: Launch any combination of scripts or executables in a single line using the intuitive ::: separator. Quoting, environment variables, and script expansions are handled for you.
Smart env handling: Apply global flags with --args/-a, then fine-tune each command with its own variables. Local overrides always win, so tweaking command-specific settings is effortless.
Package-script aware: Referencing dev, serve, or another package script? bun-tasks automatically expands it to bun run <script>, keeping your commands DRY.
Safe programmatic API: Import the exported BunTasksCLI class for custom orchestration inside your own tools—nothing auto-executes on import.

Getting Started

Install the CLI (and make sure Bun is installed first):

bun add -D bun-tasks

Add a script that fans out to multiple tasks:

{
  "scripts": {
    "dev": "bun-tasks --args NODE_ENV=dev api ::: docs --args PORT=4000"
  }
}

Define your commands in package.json or point to executables directly:

{
  "scripts": {
    "api": "bun run src/api.ts",
    "docs": "bun run docs:watch"
  }
}

Run it:

bun run dev

bun-tasks merges your environment variables, launches both tasks in parallel, and prefixes their output—so you know exactly which command produced which logs.

Advanced Usage

Need fine-grained control? Import the CLI class:

import { BunTasksCLI } from "bun-tasks";

const cli = new BunTasksCLI();
await cli.run(["echo", "hello", ":::", "echo", "world"], {
  stdoutPrefix: (index) => `[job-${index}]`,
  mirrorStderrToStdout: true,
});

Customize prefixes, control stream mirroring, or embed bun-tasks inside a larger automation script.

Built with Trust

The codebase ships with full Bun test coverage (coverage display is fully supported on Linux/WSL; Windows coverage is still maturing). The CLI lives at bin.ts, and build artifacts are carefully curated—no .d.ts.map clutter.

Acknowledgements

Portions of this project were authored with assistance from GPT-5-Codex.

Ready to simplify your Bun tooling? Dive into the docs and examples on GitHub:

npm: https://www.npmjs.com/package/bun-tasks
GitHub: https://github.com/gxy5202/bun-tasks

Give bun-tasks a spin and keep your Bun workflow fast, clean, and parallel.

DEV Community: GXY Gomi

Addfox 0.2.0: Architecture Refactoring & Dependency Slimming

Addfox 0.2.0: Architecture Refactoring & Dependency Slimming

Dependency Slimming & Supply Chain Security

Before vs. After: Third-Party Runtime Dependencies

Introducing @addfox/launcher

HMR Plugin Refactoring

Enhanced Test Coverage

Official Release

Addfox: Build Better Browser Extensions for Developers and AI

⚡ What is Addfox?

📦 Current status

Supercharge Your Bun Workflow with bun-tasks

Supercharge Your Bun Workflow with bun-tasks

Why bun-tasks?

Getting Started

Advanced Usage

Built with Trust

Acknowledgements

Introducing `@addfox/launcher`

Supercharge Your Bun Workflow with `bun-tasks`

Why `bun-tasks`?