Skip to content
Rush Commerce
Software & Dev3 min read

AI cost of JavaScript frameworks: Angular costs 86% more

Nolan Lawson had an AI agent build one app in 12 JavaScript frameworks. Hono+htmx cost $2.67 a run, Angular $4.97. What it means for your stack choice.

Your framework choice now has a line item. Developer Nolan Lawson had a coding agent build the same app in 12 frameworks and measured what each cost. In his AI cost of JavaScript frameworks benchmark, the median Hono+htmx build cost $2.67 in API-price terms. Angular cost $4.97. That is about 86% more for an app that does the same job.

What actually happened

Lawson's setup, from his write-up and the public benchmark repo:

  • The app: a small Pokémon browser on PokéAPI with search and filters. Content-heavy, light on interactivity.
  • The agent: Claude Opus 5.5 on high effort, five runs per framework, median reported. Each got its framework's official MCP server or skills where one existed.
  • The frameworks: Angular, Astro, Gracile+Lit, Hono+htmx, Next.js, Nuxt, Qwik, React Router, SolidStart, SvelteKit, TanStack Start and plain Vite.

The results:

  • Cost: Hono+htmx was cheapest at $2.67. Angular ($4.97), Gracile+Lit ($4.65) and SvelteKit ($4.28) were the most expensive.
  • Time: Astro finished fastest at 8.2 minutes. Angular was slowest at 17.2.
  • Tokens: Nuxt used the fewest, 3.85M. Angular used the most, 9.76M.
  • Code: Hono+htmx did the job in 1,370 lines. Angular needed 2,009.
  • Quality: every framework scored 100 on Lighthouse accessibility, and performance ranged from 97 to 100.

Lawson flags the caveats himself. It is one small app. Agent runs vary. Two Angular runs failed the spec. Lighthouse favors multi-page apps, which is where htmx and Astro live. He also suspects SvelteKit cost more because agents kept reading its migration guide.

Why the AI cost of JavaScript frameworks matters for your business

A $2 gap is small. Multiplied, it is not. One build is pocket change. A team running agents on every ticket, every day, pays that gap on every task. More tokens also means more wall-clock time and more chances for the agent to wander.

Boring stacks are cheap stacks. Less code, fewer abstractions and server-rendered pages gave the agent less to read and less to break. For most small-business sites, that is the right shape anyway.

Test on your own codebase. Do not switch frameworks on one benchmark. Run your agent on five real tickets, log tokens and minutes, and compare. That number is the one that goes in your budget.

Key takeaways

  • Nolan Lawson had Claude Opus 5.5 build one app in 12 JavaScript frameworks, five runs each
  • Median cost ran from $2.67 (Hono+htmx) to $4.97 (Angular), in API-price terms
  • Astro was fastest at 8.2 minutes; Angular used the most tokens at 9.76M
  • All frameworks hit 100 on accessibility, so the cost gap did not buy better output
  • It is one small app: measure your own agent's cost per ticket before you switch

Want to know what your agents actually cost per ticket? We pick stacks on evidence, not hype, and build lean systems that both your team and your coding agents can work in cheaply. Run the numbers with our ROI calculator, or talk to us about your stack.

Sources: Nolan Lawson: The AI cost of JavaScript frameworks, agent-framework-benchmark on GitHub.

  • #javascript frameworks
  • #ai coding agents
  • #benchmark
  • #htmx
  • #astro
TR

Tommy Rush — Founder, Rush Commerce

Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More

Get The Rush Report weekly — one email, zero fluff.