How to fix npm ERR! code ENOTSUP npm ERR! notsup Unsupported platform for package: wanted {"os":"linux"} (current: {"os":"win32"}) in npm

Look at the error message to see what platform the package wants:

Unsupported platform for [email protected]: wanted {"os":"!win32"} (current: {"os":"win32"})

The !win32 means "not Windows". Check the package's npm page or GitHub for platform-specific alternatives.

Many packages have alternatives for different platforms:

| Package | Alternative for Windows |
|---------|------------------------|
| n | nvm-windows or fnm |
| fsevents | Not needed (macOS only) |
| unix-specific CLIs | WSL (Windows Subsystem for Linux) |

For example, instead of n, use nvm-windows:

# Install nvm-windows from https://github.com/coreybutler/nvm-windows
nvm install 20
nvm use 20

Windows Subsystem for Linux lets you run Linux tools natively:

# Install WSL (PowerShell as Admin)
wsl --install

# Then in WSL terminal
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash
nvm install 20

WSL provides a full Linux environment where most npm packages work without modification.

Some packages like fsevents are optional and only needed on specific platforms. Warnings about them are usually safe to ignore:

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected]

These warnings don't prevent installation—they just indicate a platform-specific optimization won't be available.

You can bypass platform checks, but the package likely won't work:

npm install <package> --force

Warning: This installs the package but doesn't make it compatible. Only use this if you know the package will work despite the warning.

If you're getting ENOTSUP in Vagrant with Node.js 18.18+:

1. Move your project out of Vagrant shared folders
2. Or run npm install on the host machine
3. Or downgrade to Node.js 18.17 or earlier

This is a known issue with Node.js socket operations on VirtualBox shared folders.