Install TypeScript on Windows 11
| Install Node with winget | |
| Verify Node and npm | |
| Add TypeScript globally | |
| PATH notes |
Install Node with winget
TypeScript runs on Node, so install Node first. On Windows 11 the simplest route is winget from PowerShell or Terminal. The package already bundles npm, so one command sets up both tools:
winget install -e --id OpenJS.NodeJS
Allow the installer to finish, then open a fresh terminal window. A fresh window picks up the new entries for Node and npm without extra setup.
When winget is not available, get the long term support build from nodejs.org as plain text search result and run the installer by hand. Both routes lead to the same verify step below.
Verify Node and npm
Confirm that Node and npm answer from the new terminal. Two short commands print version numbers:
node -v
v20.11.0
npm -v
10.2.4
Version numbers mean the install worked. When the terminal reports that a command was not found, reinstall Node and open another fresh terminal before trying again.
Add TypeScript globally
Add one global copy of TypeScript with npm. The g flag makes tsc visible in every folder on the machine:
npm i -g typescript
added 1 package in 2s
tsc --version
Version 5.4.5
Any recent version number is fine for this course. When tsc stays unknown after install, close the terminal completely and open it again.
PATH notes
Windows finds programs through PATH, which is a list of folders searched in order. The Node installer extends that list automatically, so no manual edit is needed in most cases.
When tsc still fails after a fresh terminal, log out and log back in, then repeat the version checks. A reboot clears the rare case where the old PATH value stays cached in open windows.
Next: Install TypeScript on Ubuntu
Article author: Arthur Isaev