Manual Setup
Use this when the quick path fails (Corepack disabled, wrong Node, or first-time Windows PATH issues). Prefer Tooling + Getting started when things work.
Prerequisites
-
Node.js 24.x
-
pnpm 11.17.0 via Corepack (not a global npm install of pnpm)
-
PowerShell 7+ recommended on Windows
-
Accounts: Square Developer, Radar SDK, Convex
Steps
-
Clone and enter the repo
git clone <repo_url> cd ftn-site -
Confirm Node 24
node -vExpect
v24.…. If not, install/switch Node 24 before continuing (native modules depend on it). -
Enable Corepack and activate the root pnpm pin
Corepack reads the root
packageManagerfield. Activate that version explicitly:corepack enable corepack prepare pnpm@11.17.0 --activate pnpm --versionDo not run corepack use pnpm@…only undersite-nextjs/. Nested packages no longer carry their ownpackageManagerfield; the workspace pin is root-only. -
Install dependencies at the repository root
pnpm installIf pnpm reports ignored builds / needs approval:
pnpm approve-buildsThat updates
pnpm-workspace.yaml→allowBuilds(pnpm 11). There is nopackage.json#pnpmsettings block anymore.If pnpm fails with
ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION, verifypnpm-workspace.yamlincludesminimumReleaseAge: 0(this repo pins it) and re-runpnpm installfrom the repo root. -
Configure environment variables
cd site-nextjs copy .env.example .env.local -
Start Convex (separate terminal,
site-nextjs)pnpm exec convex dev -
Start Next.js (
site-nextjs)pnpm dev
After schema changes (Convex)
Run pnpm exec convex dev from site-nextjs until the deployment syncs, or deploy Convex in CI before relying on production builds.
Set NEXT_PUBLIC_APP_URL for sitemap and social preview URLs.
Still stuck?
-
Tooling checklist — four workspace members, Corepack, ABI mismatches.
-
Confirm you are not mixing a globally installed pnpm 10 with Corepack pnpm 11 (
Get-Command pnpm,pnpm --version).