Skip to main content

Install Node.js, npm, Git, and PowerShell

Spec-Up-T itself uses the same commands on every operating system (npx, npm, git, cd). What differs is how you install the tools and which terminal you open.

This page covers macOS and Windows. Linux users can follow the same verification steps; install the tools with your distribution’s package manager.

What you need​

ToolPurposeNotes
Node.js (18.x or later, LTS recommended)Runs Spec-Up-TInstaller includes npm
npmInstalls packages and runs scriptsBundled with Node.js — no separate install
GitClone, commit, and push repositoriesRequired for GitHub workflows
TerminalWhere you run commandsmacOS: Terminal; Windows: PowerShell or Windows Terminal
PowerShellShell on Windows (optional on macOS)Preinstalled on Windows 10/11

After installing, close and reopen your terminal so PATH updates take effect.

macOS​

Open a terminal​

Use Terminal (Applications → Utilities → Terminal), or the integrated terminal in Visual Studio Code.

Install Node.js and npm​

Option A — Official installer (simple)

  1. Go to https://nodejs.org.
  2. Download the LTS macOS installer.
  3. Run the .pkg and follow the prompts.
  4. npm is installed automatically with Node.js.

Option B — Homebrew

If you use Homebrew:

brew install node

Install Git​

macOS often already has a Git stub. Install the full tools with one of these:

Option A — Xcode Command Line Tools

xcode-select --install

Option B — Homebrew

brew install git

Option C — Official installer

Download from https://git-scm.com/download/mac.

Install PowerShell (optional)​

macOS does not need PowerShell for Spec-Up-T. If you want it anyway:

brew install --cask powershell

Or follow Microsoft’s guide: Installing PowerShell on macOS.

Start it with:

pwsh

Verify on macOS​

node -v
npm -v
git --version

You should see a Node.js version 18 or higher, an npm version, and a Git version. Then continue with Local Installation or Clone an Existing Repository.

Windows​

PowerShell (your terminal)​

On Windows, you run Spec-Up-T commands in a shell. PowerShell is the recommended shell: it is Microsoft’s modern command-line environment for installing software, navigating folders, and running node, npm, and git.

tip

Command Prompt (cmd.exe) can run many of the same commands, but PowerShell is the better default on modern Windows. You can also use the integrated terminal in Visual Studio Code — set the default profile to PowerShell if you like.

Windows PowerShell 5.1 is already installed on Windows 10 and 11. Open it from the Start menu by searching for Windows PowerShell.

For PowerShell 7+ (the current cross-platform shell; optional but recommended):

Option A — Microsoft Store

Search for PowerShell in the Microsoft Store and install it.

Option B — Installer

See Installing PowerShell on Windows.

Option C — winget (if winget is already available in your current PowerShell window)

winget install Microsoft.PowerShell

Start PowerShell 7 with:

pwsh

Use this PowerShell window for the install steps below.

Install Node.js and npm​

Option A — Official installer (simple)

  1. Go to https://nodejs.org.
  2. Download the LTS Windows installer (.msi).
  3. Run the installer.
  4. Accept the defaults. Leave npm and any “necessary tools” / PATH options enabled.
  5. npm is installed automatically with Node.js.

Option B — winget

In PowerShell:

winget install OpenJS.NodeJS.LTS

Install Git​

Option A — Official installer

  1. Download Git for Windows from https://git-scm.com/download/win.
  2. Run the installer.
  3. Defaults are fine for most users. Ensure Git is added to your PATH (default).

Option B — winget

In PowerShell:

winget install Git.Git

Verify on Windows​

important

After installing Node.js or Git, close PowerShell completely and open a new window (if you use VS Code’s terminal, quit and restart VS Code). The installer updates PATH, but an already-open terminal does not pick that up — so node, npm, or git may look “not recognized” until you start a fresh session.

A full PC reboot is rarely needed; try a new terminal first.

In the new PowerShell window:

node -v
npm -v
git --version

You should see a Node.js version 18 or higher, an npm version, and a Git version. Then continue with Local Installation or Clone an Existing Repository.

If npm says “running scripts is disabled”​

PowerShell may block Node’s npm.ps1 helper. Allow local scripts for your user account:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

Confirm with Y if prompted, then run npm -v again.

Alternatively, use Command Prompt (cmd) instead of PowerShell, or call npm.cmd -v — those do not use the PowerShell script.

Do Spec-Up-T commands differ by OS?​

No — once the tools are installed, the same commands work everywhere:

npx create-spec-up-t my-spec-up-t-website
cd my-spec-up-t-website
npm install
npm run menu

Minor OS differences you may notice:

  • Paths: macOS/Linux use /; Windows often shows \, though many tools accept /.
  • Shell features: quoting and some builtins differ between bash/zsh and PowerShell; Spec-Up-T’s npm scripts are written to work in common shells.
  • WSL: If you use WSL2, prefer a bash terminal profile in VS Code rather than PowerShell for that Linux environment. See Troubleshooting.