What coding agents choose in a JavaScript project

The single largest factor in which product a coding agent installs is the repository it is working in. Language is the biggest part of that. This page is what the numbers look like inside JavaScript codebases.

What coding agents choose in JavaScript

Each row is at least 25 judged sessions inside a JavaScript codebase. Categories with fewer are left out rather than reported thin.

Read the single-codebase rows as one repository, not as JavaScript. 12 of these 19 categories ran on one JavaScript codebase, because the panel only had one with that seam open. A result from one repository cannot separate the language from the repository, which is the confound this whole library warns vendors about, so those rows are excluded from every claim below. They are: code sandboxes, search, document processing, agent frameworks, code review, internationalization, message queues, usage-based billing, voice agents, ai gateways, email sending, ai sre.

The same leader, a different grip

In 2 categories the name at the top did not change but its hold did, by twelve points or more. That is still a different market.

A leader that is stronger here has the JavaScript templates and the JavaScript documentation right. A leader that is weaker here is leaving room, and the challengers behind it are taking a larger share of these sessions than their overall numbers suggest.

Where JavaScript disagrees with the overall result

3 categories. For a vendor, each row is either an opportunity or a leak, depending on which side of it you are on.

Deployment. In JavaScript codebases the agents chose Render most often, in 58% of 169 sessions. Across all languages the leader is Vercel at 39%. See the Deployment playbook.

Authentication. In JavaScript codebases the agents chose Clerk most often, in 31% of 137 sessions. Across all languages the leader is Auth0 at 25%. See the Authentication playbook.

Serverless compute. In JavaScript codebases the agents chose Vercel Functions most often, in 46% of 118 sessions. Across all languages the leader is AWS Lambda at 24%. See the Serverless compute playbook.

Where agents write it themselves in JavaScript

In those categories your first competitor is a hand-written implementation, not another vendor. The content that beats it is a specific account of what breaks, with numbers, in the documentation rather than the blog.

The codebase column is there because 2 of those rows come from one repository, and a single repository can have its own reason for writing code rather than adopting a product. Weigh them accordingly.

Why the split matters

3 leaders swapped and 2 held their place with a different grip, out of the 7 categories measured across more than one codebase. Nobody changed a product or rewrote a page between those sessions.

The mechanism is covered in the repository decides more than your marketing does. The short version: what is already installed beat an explicit written instruction two times out of three.

If you sell into JavaScript

Split your own install share by language before you read it. A vendor in product analytics looking at 56% overall is looking at 88% here, across 2 codebases. Then ship an official JavaScript template for the stacks your users run, and check your package name in the JavaScript registry against your product name.

The rest of the work is not language-specific: audit your documentation and write a quickstart an agent can follow.

How this was measured

The 1,764 JavaScript sessions are part of a published set of 15,287, run with real coding agents inside realistic codebases and judged blind. Full method: how we measured this. Every run is on the sector boards.

<!-- generated by scripts/write-data-pages.mjs -->