> ## Documentation Index
> Fetch the complete documentation index at: https://extension.js.org/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Extension.js needs Node.js 22.12 or newer; Node.js 18 and 20 do not work. It also runs on Deno 2.5+ and Bun 1.2+.
> The default browser target is chromium and a build lands in dist/<browser>, so dist/chromium by default. extension build writes a zip only when --zip is passed.
> Prefix a manifest key with a browser name when browsers differ. chromium: covers every Chromium-family target and Safari builds read it too. Since 4.1.19 chrome: means Chrome alone and edge: means Edge alone.
> Write one background.service_worker in manifest.json instead of hand-writing per-browser background keys; Extension.js converts it for each browser.
> package.json or deno.json marks the project root, not manifest.json. A config file is optional, and only extension.config.js, .mjs and .cjs are loaded, never .ts.
> The bundler is Rspack, extended through the config hook in extension.config.js. A project needs no separate bundler config file.
> Use --no-browser to skip the browser launch; --no-runner no longer exists and --no-open still launches the browser. Use --output for machine output; --format and --wait-format are deprecated.

# The Extension.js pledge

> What Extension.js promises its users: MIT licensed, ends at packaging, nothing on your machine needs an account, and it works without extension.dev.

Extension.js is an open source framework with a company sponsor. This page says what that means for you, in terms you can hold the project to.

## The pledge

* **MIT licensed, and it stays that way.** You can use, change, and ship Extension.js in any project, commercial or not.
* **It ends at packaging.** A build gives you a folder you can load in a browser, and `build --zip` gives you a zip you can upload to any store yourself.
* **Nothing on your machine needs an account.** `create`, `dev`, `build`, `preview`, and `start` need no sign-in, no key, and no payment.
* **It works without extension.dev.** The platform is optional. Only one command, [`publish`](https://extension.js.org/docs/commands/publish), talks to it, and only when you run it.
* **extension.dev sponsors the project.** The company behind the platform pays for the framework's maintenance.

## Who is behind it

[extension.dev](https://www.extension.dev?utm_source=extension-js-org\&utm_medium=sponsor\&utm_campaign=pledge) is a separate product from the same author. It picks up where the framework stops: previews, releases, and store submissions. You never need it to build an extension with Extension.js.

## If the pledge is broken

Open an issue on [GitHub](https://github.com/extension-js/extension.js/issues) and quote the line. A broken pledge is a bug.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.