Framework
standardagents/arrow-js avatar
standardagents/arrow-js

ArrowJS's own premise is that an agent can write it, and its full install leaves out the sandbox

The first UI framework for the agentic era — tiny, performant, with WASM sandboxes for safe code execution.

3,784 stars93 forksTypeScriptMIT

At a glance

What is it?
ArrowJS is a small TypeScript reactive UI runtime built around template literals and the DOM, split into five published packages with server rendering, hydration and a QuickJS sandbox. It is aimed at coding agents first and human developers second, and the page says so in its opening line.
Who is it for?
ArrowJS fits a team whose UI is being generated by a model and needs something narrow enough to read in one sitting, with the sandbox as the reason to prefer it over a general framework. It does not fit a project that needs a documented migration path from another framework or a published performance claim to lean on.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 137 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • standardagents/arrow-js3,784 ★ · +16
Star history
Repository2026-09-242026-11-15
standardagents/arrow-js3.8k3.8k

16 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The premise is that an agent can write the code, and there is an install path for that

The opening sentence says the runtime is built around platform primitives that coding agents deeply understand, and names them: JavaScript modules, template literals and the DOM. A later paragraph adds a fourth target, an agent.

There is an install route built for it. Alongside the ordinary package installs:

sh
npx @arrow-js/skill

The page describes this as equipping your preferred coding agent to add Arrow to an existing project. So the distribution strategy has a channel for a model and channels for a human, and the repository carries an AGENTS.md at its root to match.

That framing also tells you what to expect from the API surface. The core package is described as reactive state, tagged-template rendering, components, pick() and props(), and nextTick(). Five things, no plugin registry and no virtual DOM diffing algorithm in the list, which is a small enough surface for a model to hold in context.

The sandbox runs QuickJS in WASM off the host window realm

The package list describes @arrow-js/sandbox as a QuickJS/WASM-backed runtime for executing Arrow code off the host window realm while rendering into the real DOM.

That sentence is the whole design in one clause. The code an agent writes does not get the page's own globals, and it does not need a separate rendering target either, because the output still lands in the real document. The isolation is in the execution realm, not in the rendering.

The repository is built around that claim rather than around a generic sandbox story. There is a second Playwright configuration, playwright.sandbox.config.ts, beside the main playwright.config.ts, and a separate end-to-end script for it. Two test configurations means the sandbox is a thing with its own runtime behaviour to verify.

And then the install commands do not mention it. The command the page labels the full SSR and hydration stack is:

sh
pnpm add @arrow-js/core @arrow-js/framework @arrow-js/ssr @arrow-js/hydrate

Four packages, and the sandbox is not one of them.

Four install paths, from a Vite 8 scaffold to a bare esm.sh import

Four routes are given, and they are genuinely different rather than four spellings of the same thing.

The scaffold for a new application is one line:

sh
pnpm create arrow-js@latest arrow-app

The page says it creates a complete Vite 8 Arrow app with SSR, hydration and the full framework stack. Naming a major version of the bundler in a scaffolder is a useful detail, because it is the version you will be locked into.

Then the core-only install, npm install @arrow-js/core, which is the smallest thing the framework can do. And finally the full stack command above.

The fourth route has no package manager in it at all. For the core runtime no build step is required, and a page can import it as a module:

html
<script type="module">
  import { html, reactive } from 'https://esm.sh/@arrow-js/core'
</script>

That is a CDN import from a third-party host, which is the shortest path from nothing to a running reactive element and also the one that puts a third party in the trust path of every page that uses it.

core is DOM-first, and the other packages only add stages

The layering is stated as four bullets. @arrow-js/core stays DOM-first and framework-agnostic. @arrow-js/framework adds async render tracking and boundaries, with boundary(), render(), toTemplate() and document rendering helpers. @arrow-js/ssr renders HTML and serialises async payloads on the server through renderToString() and serializePayload(). And @arrow-js/hydrate adopts existing SSR output in the browser rather than replacing it, through hydrate() and readPayload().

There is one ordering rule and it is a real constraint: async components use the same component() API, but the async runtime from framework, ssr or hydrate has to be imported before rendering. That is a runtime dependency expressed as an import order rather than as a build-time check, so a mis-ordered module surfaces as a behaviour difference at render time.

The core example is eleven lines. A component function creates reactive state, returns an html template with an @click attribute bound to a closure over the state and an interpolation that reads it, and the rendered result is applied to document.body.

Eight benchmark scripts and a performance plan the page never mentions

The page's development section lists four commands: pnpm dev for the docs app, pnpm test for Vitest, pnpm test:e2e for Playwright and pnpm typecheck.

The workspace package has a great deal more. There are eight benchmark scripts, from setup through sync, smoke, core, targets and breadth presets to a run and an analyse step, all pointing at a harness under bench/js-framework-benchmark. There is a verify script that chains typecheck, test and build, an install:browsers step for Playwright, a smoke:create-arrow-js script that exercises the scaffolder, and release scripts.

So a benchmark suite against other JavaScript frameworks is a first-class part of this repository, and PERF_PLAN.md sits at the root next to it. None of that reaches the page.

That matters because the description calls the runtime tiny and blazing-fast and the README calls it type-safe, and the page carries no number for any of those. The evidence is in the repository rather than in the documentation, which is the arrangement the project's own premise would predict.

The visible release history jumps two years and the tag prefix changed

Three releases are listed. v1.0.6 on 2026-04-01, v1.0.5 on 2026-03-31, and an alpha, 1.0.0-alpha.10, on 2024-02-21.

Two things to notice. The two recent tags carry a v prefix and the alpha does not, so the tagging convention changed at the 1.0 boundary. And the gap between the alpha and v1.0.5 is more than two years, with nothing from the intervening period in the list of recent releases.

The last push to main is dated 2026-07-01, three months after the newest tag. The private workspace package carries version 1.0.6, the same number as the newest release, so the workspace version tracks the published line rather than sitting independently of it.

The Node floor is written as a two-range expression, >=20.19.0 or >=22.12.0, which accepts the current long-term line and the current release line while excluding the versions in between the two lower bounds.

Support is one Discord, one issue tracker and one account on X

The community section is three lines: a Discord for questions and to see what others are building, GitHub Issues for bugs and feature requests, and an X account to follow for updates and releases.

That third line is the one to notice. Release announcements go out through a personal account rather than through a feed in the repository, and the page is explicit that this is where updates and releases are posted. The repository has no releases page of its own to point at.

Editor support is a single VS Code extension, published under the StandardAgents publisher with the name ArrowJS Syntax, whose stated job is syntax highlighting and autocomplete inside html template literals. Highlighting inside a tagged template is the specific problem an extension has to solve here, because the framework's syntax is ordinary JavaScript with markup in it.

The rest of the root is ordinary: an .eslintrc alongside a prettier config and two ignore files, two TypeScript configs with a base, a vitest config, a pnpm workspace file, a scripts directory, a tests directory, and test-results committed alongside them.

Editorial conclusion

ArrowJS fits a team whose UI is being generated by a model and needs something narrow enough to read in one sitting, with the sandbox as the reason to prefer it over a general framework. It does not fit a project that needs a documented migration path from another framework or a published performance claim to lean on. Check three things first. Whether you need the sandbox, because the command the page calls the full SSR and hydration stack installs four packages and leaves @arrow-js/sandbox out. Which Node you are on, since the workspace asks for 20.19 or 22.12 and up. And which release you are installing, because the visible history jumps from an alpha in February 2024 to v1.0.5 in March 2026.

Frequently asked questions

What is ArrowJS?

A small, type-safe reactive UI runtime built around JavaScript modules, template literals and the DOM, described by its own page as built around primitives that coding agents deeply understand. The core package provides reactive state, tagged-template rendering, components, pick(), props() and nextTick().

How do I install ArrowJS in an existing project?

With npx @arrow-js/skill, which the page describes as equipping your preferred coding agent to add Arrow to an existing project. For a new application, pnpm create arrow-js@latest scaffolds a Vite 8 app with SSR and hydration, and the core package alone installs with npm install @arrow-js/core.

What does the ArrowJS sandbox package do?

It is a QuickJS/WASM-backed runtime that executes Arrow code off the host window realm while rendering into the real DOM. It ships separately as @arrow-js/sandbox and is not in the command the page calls the full SSR and hydration stack.

Does ArrowJS need a build step?

Not for the core runtime. The page shows a module script importing html and reactive from an esm.sh URL directly in the browser, and a separate Vite plugin package, @arrow-js/vite-plugin-arrow, for projects that do use a bundler.

Which Node versions does ArrowJS require?

The workspace package declares >=20.19.0 || >=22.12.0, pins pnpm 10.14.0 as its package manager and is an ES module package. Tests run on Vitest, with Playwright for end-to-end runs and a second Playwright configuration for the sandbox.

What is the latest ArrowJS release?

v1.0.6, published 2026-04-01, after v1.0.5 on 2026-03-31 and an alpha, 1.0.0-alpha.10, from 2024-02-21. The last push to main is dated 2026-07-01.

Official sources

  1. License: MIT
  2. Project website
  3. README
  4. Releases
  5. standardagents/arrow-js on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/standardagents-arrow-js.svg)](https://hysenlabs.com/projects/standardagents-arrow-js)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/standardagents-arrow-js.svg)](https://hysenlabs.com/projects/standardagents-arrow-js)

Was this useful?