CloveJSFiles in, routes out.

The backend framework that configures itself. CloveJS brings Next.js/Nuxt-inspired file-based routing to Node.js — your folder structure defines your routes, services, middlewares and injectables, fully typed, with zero manual registration.

Get started

What is CloveJS?

View on GitHub

🗂️

Nothing to wire up

Next.js/Nuxt-inspired file-based routing for your backend. Drop a file into api/, ws/, services/, di/ or middlewares/ and it is live. No decorators, no module graph, no registration calls.

Project structure

🧩

DI in the box

Singleton, session and request lifetime scopes, resolved for you. Singletons are ready before the first request lands.

Lifetimes

🔤

TypeScript from the box

Fully typed, automatically, from generated declarations — one entry per file in services/ and di/, written by a path-level scan that never executes your code.

Typed context

🔌

WebSockets included

Files in ws/ map to socket endpoints exactly like routes do, [param] segments and per-connection containers included.

WebSockets

🤝

Adopts incrementally

Mount Clove inside an Express app you already have and migrate routes over at your own pace.

Express interop

⚡

Fast feedback loop

clove dev watches files, regenerates types and reloads. Boot-time convention violations name the exact file to fix.

CLI reference

Sixty seconds to a running API

bash

npm i clovejs
npx clove scaffold      # create the default project structure
npm run dev

Create src/api/v1/users/[id].get.ts:

import { get } from "clovejs"

export default get(async (req, res, ctx) => {
  return ctx.users.findById(Number(req.params.id))
})

GET /api/v1/users/1 now returns JSON. No router file was edited, and ctx.users is typed because a file exists at src/services/users.ts.

Bring your assistant along