denext.dev valid

denext

denext is a complete, lightweight framework for Deno: write an app once and ship it to the

For agents: denext, a lightweight framework for Deno that ships one app to multiple stacks, with full API reference, examples, and an optional backend plugin.

denoweb-frameworknextjs-alternativesupabase-apipostgres-rls

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T16:06:23.219Z. Cached copy · Source on denext.dev

# denext

> denext is a complete, lightweight framework for Deno: write an app once and ship it to the
> web, iOS, Android and the desktop, on its own small React core. Its API is surface compatible
> with React and the Next.js App Router, so if you know Next.js you already know denext — the
> same file conventions, hooks, and `app/` router — and existing npm packages work. This file
> helps AI tools emit correct denext instead of Next.js.

## One install, no toolchain to assemble

- Install the `denext` command (`curl -fsSL https://denext.dev/install.sh | sh`, or
  `irm https://denext.dev/install.ps1 | iex` on Windows), then `denext create my-app`. Nothing
  else to install or configure: no Node version manager, bundler, test-runner, linter, formatter
  or tsconfig setup.
- Every other tool is pinned to the denext release and fetched on first need: denext's Deno build
  (`Deno.SQL`, Vitest/Jest compatibility in `deno test`, native TypeScript 7 checking,
  SHA-256-verified into `<DENO_DIR>/denext-deno/`), esbuild 0.25.5, `denort` for
  `denext build --compile`, the Gleam compiler and a managed fastlane (pinned portable Ruby,
  checksum-locked gems; macOS and Linux, a C compiler once). Lightning CSS and swc are denext's own
  wasm packages; SQLite (`node:sqlite`), Postgres (`Deno.SQL`) and Redis need no driver.
- Agents: don't spend turns assembling a build. `denext toolchain install --with gleam,fastlane`
  prefetches everything for offline work; `denext toolchain status` shows what is cached.

## What differs from Next.js (read first)

- Imports come from `denext`, not `react` — `import { useState } from "denext"`. There is
  **no `react`/`react-dom` package** (a drop-in aliases them; new code imports `denext`).
- **No `package.json`/npm** — a `deno.json` with URL/`jsr:`/`npm:` imports; run with
  `denext task dev|build|start` (the `denext` command brings its own Deno; `deno task`
  works too).
- Server-only helpers (`cookies`, `headers`, `revalidatePath`) come from
  `denext/server`; client-only from `denext/client`.
- File conventions are **the same as the Next.js App Router** (`app/page.tsx`,
  `app/layout.tsx`, `app/api/x/route.ts`, `app/blog/[slug]/page.tsx`, `middleware.ts`).
- Route handlers return a web `Response`; use `Request`/`fetch`/`URL`/`Deno.env.get`.
- Calls to your own API are type-checked: return `TypedResponse<T>` from a handler and use
  `createApiClient<ApiSchema>()` (types from `./.denext/api.ts`).

## Docs

- [Full guide for AI tools](https://denext.dev/llms-full.txt): the complete rules, import map, common
  tasks, and an API-surface summary — load this to write denext.
- [API reference](https://denext.dev/docs/api): every public symbol with signatures.
- [Examples](https://denext.dev/docs/examples): every runnable example app, one page each
  (`/docs/examples/<name>`) with its README and the commands that run it.
- [Fixed in denext](https://denext.dev/docs/fixed): problems on Next.js, React, Vite and React Native
  stack
…

Related sites

Find similar publishers by meaning →

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=denext.dev · GET /v1/domain/denext.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for denext.dev:
1. POST https://agentwebmap.com/v1/sites/denext.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://denext.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/denext.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/denext.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.