Verification Checklist

Run through every check to confirm Node.js and Git are correctly installed and configured before your first session.

Work through every item below. Each check runs a specific command and tells you exactly what output to expect. If you see that output, the check passes. If you see something different, the troubleshooting notes tell you what to do next.

Open Git Bash for all checks below. You can also use Command Prompt or PowerShell — but Git Bash shows the most consistent output.

All checks should pass before Session 1. If any check fails, don't spend more than 10 minutes trying to fix it alone. Screenshot the error output and send it to the WhatsApp group. Most failures are one simple fix away.

Node.js Checks

Check 1 — Node.js is installed

Run:

Expected output:

The exact patch number (the last .0) may differ. What matters: the version starts with v20. or higher.

Check — if you see a version number starting with v20. or higher, Node.js is installed correctly. Move to Check 2.

If you see 'node' is not recognized:

Close the terminal you're using and open a brand new one
If the error persists, restart your computer
If it still fails after restarting, the installation did not complete correctly — uninstall Node.js from "Add or Remove Programs," restart, and reinstall using the steps on the Node.js Installation page

Check 2 — npm is installed

Run:

Expected output:

Any version starting with 10. is correct for Node.js 20. If you're on Node.js 22, you may see 10.9.x.

Check — you should see a version number starting with 10.. If npm is recognized, proceed to Check 3.

If you see 'npm' is not recognized:

npm comes bundled with Node.js — if node works but npm doesn't, the PATH is partially configured
Reinstall Node.js ensuring the "Add to PATH" option is selected during the Custom Setup screen

Check 3 — npm can reach the internet

Run:

Expected output:

The number of milliseconds will vary — any value under 500ms is fine.

Check — you should see PONG followed by a response time in milliseconds. Any value under 500ms is fine.

If you see a network error:

Check your internet connection
If you're on a corporate network or VPN, it may be blocking npm's registry. Try disconnecting from the VPN and running the check again
If npm ping fails on a regular home connection, check your firewall settings

Check 4 — can create and run a simple Node.js script

This check confirms Node.js actually executes code — not just that it's installed.

Run:

Expected output:

Check — you should see Hello from Node.js printed on the next line. If you see this, Node.js is executing code correctly.

If you see an error:

Your Node.js installation may be corrupted. Reinstall it.

Git Checks

Check 5 — Git is installed

Run:

Expected output:

Any version from 2.30 onwards is fine. The .windows.2 suffix is normal — it's the Windows-specific build identifier.

Check — you should see git version 2.x.x.windows.x (or similar). Any version from 2.30 onwards is fine.

If you see 'git' is not recognized:

Close the terminal and open a new one
If the error persists, restart your computer
If it still fails, the Git installation did not complete the PATH update. Reinstall Git using the steps on the Git Installation page, being careful to select "Git from the command line and also from 3rd-party software" on the PATH configuration screen.

Check 6 — Git identity is configured

Run:

Expected output:

(Your actual name, not "Priya Sharma")

Then run:

Expected output:

(Your actual email address)

Check — both commands should return your actual name and email. If either is blank, your identity is not set up yet.

If either returns blank output:

Your identity is not configured. Run the setup commands from the Git Configuration page, then run the checks again.

If the email shown doesn't match your GitHub account email:

Re-run the email configuration with the correct address: git config --global user.email "your-correct@email.com"

Check 7 — Default branch is set to `main`

Run:

Expected output:

Check — you should see main (not master or blank). If you see master, run git config --global init.defaultBranch main and check again.

If you see master or blank output: run git config --global init.defaultBranch main and then run the check again.

Check 8 — Line ending behavior is configured correctly

Run:

Expected output:

Check — you should see true. If you see false or blank, run git config --global core.autocrlf true and check again.

If you see false or blank output: run git config --global core.autocrlf true and then run the check again.

Check 9 — Full configuration is readable

Run:

Expected output (scan for these lines):

All five lines should be present. Other lines in the output (starting with http., credential., or gui.) are set automatically by the installer and can be ignored.

Check — scan the output for user.name, user.email, init.defaultbranch, core.autocrlf, and core.editor. All five should be present.

If core.editor is missing: run git config --global core.editor "code --wait"

Check 10 — Git can initialize a repository

This confirms the complete Git workflow is functional — not just that the binary is installed.

Run:

Expected output:

Key things to confirm:

Initialized empty Git repository — Git init worked
On branch main — the default branch name is correctly set to main
No error messages

Check — you should see Initialized empty Git repository and On branch main. Both lines must appear for this check to pass.

Clean up after the check: run cd .. && rm -rf /tmp/git-check-test (or simply delete the folder from Windows Explorer).

Summary Table

Use this as your final sign-off checklist:

#	Check	Command
1	Node.js installed	`node --version` → `v20.x.x`
2	npm installed	`npm --version` → `10.x.x`
3	npm can reach internet	`npm ping` → PONG
4	Node.js executes code	`node -e "console.log(...)"` → output
5	Git installed	`git --version` → `2.x.x`
6	Git identity configured	`git config user.name` + `user.email` → your details
7	Default branch is `main`	`git config init.defaultBranch` → `main`
8	Line endings configured	`git config core.autocrlf` → `true`
9	Full config readable	`git config --list` → 5 required keys present
10	Git can init a repo	`git init && git status` → `On branch main`

You're Ready

If all 10 checks pass, you have a fully functional development environment for Node.js and Git. These two tools are the foundation — everything else we install (React, VS Code extensions, Supabase CLI, Claude Code) builds on top of what you've just verified.

You have completed:

Node.js 20 LTS installed and verified
npm functional and network-connected
Git installed and recognized globally
Git identity configured with your name and email
Default branch set to main
Windows line endings configured correctly
VS Code set as the Git editor
End-to-end Git workflow confirmed working

Before your first live session: Run through this checklist one more time on the morning of Session 1. Tools sometimes break when Windows updates overnight or when antivirus software flags a process. A 5-minute verification on session morning means you arrive knowing everything works — not discovering a problem after the session starts.

See you in Session 1.

Open Git Bash for all checks below. You can also use Command Prompt or PowerShell — but Git Bash shows the most consistent output.

Node.js Checks

Check 1 — Node.js is installed

Run:

Expected output:

The exact patch number (the last .0) may differ. What matters: the version starts with v20. or higher.

Check — if you see a version number starting with v20. or higher, Node.js is installed correctly. Move to Check 2.

If you see 'node' is not recognized:

Close the terminal you're using and open a brand new one
If the error persists, restart your computer
If it still fails after restarting, the installation did not complete correctly — uninstall Node.js from "Add or Remove Programs," restart, and reinstall using the steps on the Node.js Installation page

Check 2 — npm is installed

Run:

Expected output:

Any version starting with 10. is correct for Node.js 20. If you're on Node.js 22, you may see 10.9.x.

Check — you should see a version number starting with 10.. If npm is recognized, proceed to Check 3.

If you see 'npm' is not recognized:

npm comes bundled with Node.js — if node works but npm doesn't, the PATH is partially configured
Reinstall Node.js ensuring the "Add to PATH" option is selected during the Custom Setup screen

Check 3 — npm can reach the internet

Run:

Expected output:

The number of milliseconds will vary — any value under 500ms is fine.

Check — you should see PONG followed by a response time in milliseconds. Any value under 500ms is fine.

If you see a network error:

Check your internet connection
If you're on a corporate network or VPN, it may be blocking npm's registry. Try disconnecting from the VPN and running the check again
If npm ping fails on a regular home connection, check your firewall settings

Check 4 — can create and run a simple Node.js script

This check confirms Node.js actually executes code — not just that it's installed.

Run:

Expected output:

Check — you should see Hello from Node.js printed on the next line. If you see this, Node.js is executing code correctly.

If you see an error:

Your Node.js installation may be corrupted. Reinstall it.

Git Checks

Check 5 — Git is installed

Run:

Expected output:

Any version from 2.30 onwards is fine. The .windows.2 suffix is normal — it's the Windows-specific build identifier.

Check — you should see git version 2.x.x.windows.x (or similar). Any version from 2.30 onwards is fine.

If you see 'git' is not recognized:

Close the terminal and open a new one
If the error persists, restart your computer
If it still fails, the Git installation did not complete the PATH update. Reinstall Git using the steps on the Git Installation page, being careful to select "Git from the command line and also from 3rd-party software" on the PATH configuration screen.

Check 6 — Git identity is configured

Run:

Expected output:

(Your actual name, not "Priya Sharma")

Then run:

Expected output:

(Your actual email address)

Check — both commands should return your actual name and email. If either is blank, your identity is not set up yet.

If either returns blank output:

Your identity is not configured. Run the setup commands from the Git Configuration page, then run the checks again.

If the email shown doesn't match your GitHub account email:

Re-run the email configuration with the correct address: git config --global user.email "your-correct@email.com"

Check 7 — Default branch is set to `main`

Run:

Expected output:

Check — you should see main (not master or blank). If you see master, run git config --global init.defaultBranch main and check again.

If you see master or blank output: run git config --global init.defaultBranch main and then run the check again.

Check 8 — Line ending behavior is configured correctly

Run:

Expected output:

Check — you should see true. If you see false or blank, run git config --global core.autocrlf true and check again.

If you see false or blank output: run git config --global core.autocrlf true and then run the check again.

Check 9 — Full configuration is readable

Run:

Expected output (scan for these lines):

All five lines should be present. Other lines in the output (starting with http., credential., or gui.) are set automatically by the installer and can be ignored.

Check — scan the output for user.name, user.email, init.defaultbranch, core.autocrlf, and core.editor. All five should be present.

If core.editor is missing: run git config --global core.editor "code --wait"

Check 10 — Git can initialize a repository

This confirms the complete Git workflow is functional — not just that the binary is installed.

Run:

Expected output:

Key things to confirm:

Initialized empty Git repository — Git init worked
On branch main — the default branch name is correctly set to main
No error messages

Check — you should see Initialized empty Git repository and On branch main. Both lines must appear for this check to pass.

Clean up after the check: run cd .. && rm -rf /tmp/git-check-test (or simply delete the folder from Windows Explorer).

Summary Table

Use this as your final sign-off checklist:

#	Check	Command
1	Node.js installed	`node --version` → `v20.x.x`
2	npm installed	`npm --version` → `10.x.x`
3	npm can reach internet	`npm ping` → PONG
4	Node.js executes code	`node -e "console.log(...)"` → output
5	Git installed	`git --version` → `2.x.x`
6	Git identity configured	`git config user.name` + `user.email` → your details
7	Default branch is `main`	`git config init.defaultBranch` → `main`
8	Line endings configured	`git config core.autocrlf` → `true`
9	Full config readable	`git config --list` → 5 required keys present
10	Git can init a repo	`git init && git status` → `On branch main`

You're Ready

You have completed:

Node.js 20 LTS installed and verified
npm functional and network-connected
Git installed and recognized globally
Git identity configured with your name and email
Default branch set to main
Windows line endings configured correctly
VS Code set as the Git editor
End-to-end Git workflow confirmed working

See you in Session 1.

Verification Checklist

Node.js Checks

Check 1 — Node.js is installed

Check 2 — npm is installed

Check 3 — npm can reach the internet

Check 4 — can create and run a simple Node.js script

Git Checks

Check 5 — Git is installed

Check 6 — Git identity is configured

Check 7 — Default branch is set to `main`

Check 8 — Line ending behavior is configured correctly

Check 9 — Full configuration is readable

Check 10 — Git can initialize a repository

Summary Table

You're Ready

On this page

Verification Checklist

Node.js Checks

Check 1 — Node.js is installed

Check 2 — npm is installed

Check 3 — npm can reach the internet

Check 4 — can create and run a simple Node.js script

Git Checks

Check 5 — Git is installed

Check 6 — Git identity is configured

Check 7 — Default branch is set to `main`

Check 8 — Line ending behavior is configured correctly

Check 9 — Full configuration is readable

Check 10 — Git can initialize a repository

Summary Table

You're Ready

On this page