Kenzie Systems Logo

Install Node.js Windows 11

Build production-ready projects, then publish them safely.

Why Node.js is important

Node.js is the most common build toolchain for modern web applications (React, Vite, Ant Design, Next.js). On Windows 11, it lets you install dependencies, compile your source code into a production build, and publish only the final optimized output.

Production mindset
Recommended
  1. Develop your project locally.
  2. Build once it is ready: npm run build.
  3. Publish the output folder only (dist/ or build/).
  4. Serve with IIS (static) or run a Node server only when needed (SSR/API).
Important: For many projects (React/Vite), Node is needed to build. IIS can serve the final static files without running Node in production.

Install Node.js on Windows 11

The recommended method is the official Node.js Windows installer (MSI). It includes npm automatically.

Step-by-step (recommended)
Official
  1. Download Node.js from the official website (LTS recommended).
  2. Choose Windows Installer (.msi).
  3. Run the installer as a normal user (Administrator not required in most cases).
  4. Keep the defaults checked:
    • Add to PATH
    • npm package manager
    • (Recommended) Tools for native modules
  5. Finish, then open a new PowerShell window (important).
Tip: If PowerShell was open during installation, it might not see the new PATH. Close and reopen PowerShell after installing.

Double-check everything installed properly

1) Confirm versions
Required

Open PowerShell and run:

node -v npm -v

You should see version numbers (example: v20.x.x). That confirms Node.js and npm are installed.

2) Confirm PATH / location
Recommended

This confirms Windows is using the correct binaries:

where node where npm

Expected output is usually something like:
C:\Program Files\nodejs\node.exe
C:\Program Files\nodejs\npm.cmd

3) Real test: npm can create a project
Recommended
mkdir node-test cd node-test npm init -y

If you see a new package.json file, npm is working correctly.

4) Real test: production build
Production

Inside a real web project, run:

npm install npm run build

Most modern projects generate:
• Vite: dist\
• CRA: build\

Publish: Copy only dist\ or build\ to your server / IIS site folder. Do not publish your full dev folder when deploying.

Recommended downloads

Only install Node.js from trusted sources.

Official Node.js downloads
Trusted

Choose LTS if you want the most stable version for production builds.

Troubleshooting

If something does not work, these are the most common fixes.

Node/npm commands not found
Fix
  • Close all terminals and open a new PowerShell window.
  • Run where node again.
  • If still missing, reinstall Node.js and ensure “Add to PATH” is checked.
Build fails (native modules)
Fix

Some npm packages require compilation. If you enabled Tools for native modules during install, Windows can auto-install required build tools when needed.

# Rebuild native modules (inside your project folder) npm rebuild

If you installed build tools recently, restart your machine to ensure everything is loaded.

Windows 11 + IIS note
Important

IIS typically serves static files. For React/Vite apps, you usually publish the build output only. You only need Node running on a server when your project is:

  • Server-side rendered (SSR) apps like Next.js (server mode)
  • Node APIs / backend services
  • Real-time WebSocket services

Always download Node.js from the official website. Avoid unknown installers or modified distributions.