nextrs.toml

The app's single config source for identity and deployment settings

nextrs.toml at the app root is where a nextrs app is configured. It is the one file you edit; nextrs generate turns it into the provider files Vercel and Cloudflare actually read. Newly scaffolded apps ship with one.

[app]
name = "myapp"                        # names generated resources (myapp-cron)
url = "https://myapp.vercel.app"      # the deployed app, for cron triggers

[vercel]
regions = ["pdx1"]
# runtime = "vercel-rust@4.0.11"      # defaults, shown for reference
# install_command = "npm ci"
# build_command = "npm run client:prepare && cargo build --release --bin index && npm run client:build"
# git_deploys = false                 # emitted into generated local config

# [vercel.extra]                      # non-framework Vercel keys only
# trailingSlash = false

Cron schedules are colocated with their protected handlers as #[nextrs::cron(schedule = "...")]; see Cron Jobs.

What nextrs generate writes

• .nextrs/vercel.json — generated framework state containing the Rust function, the catch-all rewrite to it, immutable caching for /dist, git auto-builds off, your regions/commands, and any Vercel-provider crons. It is overwritten atomically on every generation and passed to Vercel with --local-config. The adjacent README marks it as generated. [vercel.extra] is an escape hatch for Vercel keys the table does not model, but cannot override framework-owned $schema, regions, commands, functions, headers, rewrites, git, or crons.
• .nextrs/cloudflare/ — the Worker shim for cloudflare-provider crons (gitignored, regenerated on demand).

The [vercel] table is optional; omitting it uses framework defaults. A root vercel.json is never read or mutated, so it cannot become a second source of deployment or cron configuration. If one exists, generation warns that it is ignored and explains how to copy its settings into nextrs.toml.

Moving settings from vercel.json

Copy settings that NextRS models into [vercel]:

Put other non-framework top-level settings under [vercel.extra]. For example, "trailingSlash": false becomes:

[vercel.extra]
trailingSlash = false

Do not copy $schema, functions, headers, rewrites, git, crons, or the other framework-owned keys listed above into [vercel.extra]; NextRS generates those from its typed settings and route declarations. The original file is left untouched.

nextrs deploy and nextrs cron deploy both run generate first, so the provider files can't drift from the config.

Server bundle settings

Colocated bundle.toml files assign routes and subtrees. [bundles.<name>] in nextrs.toml supplies the named bundle's Cargo features and private runtime assets; [deployment].features supplies common features. See Server Bundles for the complete build and deploy flow.