This is intentionally more than an installer checklist. The goal is that you can diagnose PATH, permissions, processes, ports, runtime versions, and package-manager failures before framework code enters the picture.
You need an editor, shell, Git, a Node version line, Corepack/pnpm, browser DevTools, and later external services such as PostgreSQL/Supabase and Docker. Treat each as a separate executable/service you can verify.
Get-Location
$PSVersionTable.PSVersionUse a normal user-level installation where appropriate. Open a fresh PowerShell after installation and prove which executable is being resolved before assuming setup succeeded.
Get-Command git
git --version
git config --global user.name
git config --global user.emailVS Code is an editor, not the runtime. Its integrated terminal inherits environment variables from the editor process, so restart the editor when PATH changes are not visible.
code --versionA version manager makes project runtimes reproducible. The repository/course may lock a specific Node line; use that lock instead of whatever global installer happens to be newest.
Get-Command node
node --version
npm --versionCorepack lets the repository declare the package-manager version. Do not maintain unrelated global pnpm installations if they cause command-resolution confusion.
corepack --version
corepack enable
pnpm --versionAvoid protected system folders. Keep project paths simple enough that scripts/tools do not inherit permission problems from Program Files or system directories.
git status
Get-LocationThe lockfile is part of the project contract. On the first install, pnpm creates pnpm-lock.yaml. Commit it. After that, use --frozen-lockfile in CI/verification so dependency resolution cannot drift silently.
pnpm installStart the dev server, read the exact listening address, and verify the browser request. If the port is occupied, find the owning process rather than killing random Node processes.
pnpm dev
Get-NetTCPConnection -State Listen | Sort-Object LocalPortDevelopment mode is not proof that the project builds. Run type checking and the production build from a clean state before pushing.
pnpm lint
pnpm buildThe documentation site itself needs no database secrets. When you build TaskFlow, use .env files excluded from Git and commit only safe examples documenting required variable names.
git status
git diff -- .gitignoreRun Get-Command pnpm, check Corepack, open a fresh terminal, and identify whether another pnpm executable shadows the intended one.
Check whether the project/tool is writing under a protected directory or another process is holding the file. Do not default to Administrator mode as the permanent fix.
Find the PID owning the listening port, identify the process, then stop only the service you actually mean to stop.
Use Get-Command node and your version manager's current selection. PATH order can point to an older standalone installation.
Read the production build error first. Server/client boundaries, type errors, static generation, and environment values often surface only during build.