npm ERR! code EBADPLATFORM — notsup Unsupported platform for fsevents: wanted {"os":"darwin"} (current: {"os":"linux"})
A package restricted to certain OS/CPU was installed as a required (not optional) dependency on another platform.
Exact message you may see
Unsupported platform for fsevents
Seen on:
npm
Meaning
fsevents is macOS-only and should be optional. Errors appear with old npm, --force installs, or packages listing it as a direct dependency.
Common causes
- Platform-specific package listed as a direct dependency
- Old npm treating optional deps as required
- Lockfile from another OS
⚡ Quick fix
- Make it optionalDependencies
- Update npm
- Regenerate the lockfile on the target platform
Detailed fix by platform
npm
npm install --omit=optional # or move fsevents to optionalDependencies
How to diagnose
- Package — Which one and wanted platform?
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 0x8007007E 0x8007007E: The specified module could not be found
- Dependency requires compileSdk Dependency 'androidx.x:1.y' requires libraries and applications that depend on it to compile against version 34 or later of the Android APIs
- E404 npm ERR! code E404 — 404 Not Found: package@version is not in this registry
Most viewed in npm
Other ways to find it
Where this error sits
Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 13 Oct 2026