Farm.js

Why it's ranked here

The scope is real and visible in the code. One core package exports routing, caching, cron jobs, schema migrations, translations, OpenAPI output and an MCP (Model Context Protocol) server for AI agents, and the root manifest wires separate browser test suites for production builds, server components, WebAssembly and devtools. Against that, the README scopes support to a 0.1 line, the compiler and native renderer are labelled experimental, and the architecture document still lists server actions and middleware as planned when the README says both ship. A wide, MIT licensed framework at an early version: worth a trial project before a production bet.

What's good

The MCP plugin is built with care. It creates a fresh server for every request, so a tool the caller is not authorised for is neither listed nor callable. It refuses to forward credential and proxy headers such as cookies, API keys, forwarded-for and Cloudflare or Vercel headers, rejects a batch whose messages resolve to different identities, and returns validation messages to the caller while treating other exceptions as private. Release rules are written down in detail, including that a prior green commit is not evidence for later changes, and a test installs the starter generator from packed tarballs outside the workspace.

Tradeoffs

Telemetry and analytics are on unless the config switches them off, and the command line tool ships commands to report and toggle that status, so teams with data policies have to opt out deliberately. The project is young: the README frames support around 0.1, and the root manifest depends on beta and release-candidate builds of its server layer, Nitro and h3. The architecture document lags the code and opens with stray characters before its title. Node 22.13 or newer is required. The headline compiler speedups come from the project's own benchmark, not an outside one.

How to use it well

Pick it if you like the Next.js App Router model but want Vite's dev server, or want Vue, Svelte or Solid behind the same routing and server functions. Start from the browser playground or a scaffolded starter, keep the experimental compiler and native rendering off until the basics hold, and turn telemetry off in config if that matters to you. It suits products that need billing, auth or email wired in early. It is the wrong choice where a stable 1.x interface and long support windows are requirements; pin exact versions and read the stability page before each upgrade.

Observed

License

MIT

Language

TypeScript

Packaging

npm packages under the @farm.js scope, built as a pnpm monorepo

Interfaces

Library, CLI (dev, build, deploy, preview, doctor, upgrade), MCP server plugin

Runtime requirement

Node.js 22.13 or newer

Renderers

React by default; Preact, Solid, Vue and Svelte adapters marked beta

Telemetry

Enabled by default; disabled by setting telemetry to false in config

Test setup

Node test runner scripts plus Playwright end-to-end suites declared in package.json

Experimental features

AOT React compiler and Strata native rendering, both labelled experimental in the README