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

  1. Clone and enter the repo

    git clone <repo_url>
    cd ftn-site
  2. Confirm Node 24

    node -v

    Expect v24.…. If not, install/switch Node 24 before continuing (native modules depend on it).

  3. Enable Corepack and activate the root pnpm pin

    Corepack reads the root packageManager field. Activate that version explicitly:

    corepack enable
    corepack prepare pnpm@11.17.0 --activate
    pnpm --version
    Do not run corepack use pnpm@… only under site-nextjs/. Nested packages no longer carry their own packageManager field; the workspace pin is root-only.
  4. Install dependencies at the repository root

    pnpm install

    If pnpm reports ignored builds / needs approval:

    pnpm approve-builds

    That updates pnpm-workspace.yamlallowBuilds (pnpm 11). There is no package.json#pnpm settings block anymore.

    If pnpm fails with ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION, verify pnpm-workspace.yaml includes minimumReleaseAge: 0 (this repo pins it) and re-run pnpm install from the repo root.

  5. Configure environment variables

    cd site-nextjs
    copy .env.example .env.local
  6. Start Convex (separate terminal, site-nextjs)

    pnpm exec convex dev
  7. 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).