How to fix 'Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

Question

Testing binary Binary is fine npm WARN rollback Rolling back node-pre-gyp@0.12.0 failed (this is probably harmless):

EPERM: operation not permitted, lstat 'C:\Users\orca yoon\Documents\IonicProjects\starters\epic\node_modules\fsevents\node_modules'

npm notice created a lockfile as package-lock.json. You should commit this file.

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\fsevents):

npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

added 1105 packages from 1050 contributors and audited 53269 packages in 445.94s found 1 high severity vulnerability run npm audit fix to fix them, or npm audit for details

Answer 1

• First,

Run your command prompt or powershell as Administrator role. Then you'll get avoided with PERMISSION ERROR.

• Second,

Ignore npm audit fix. It only suggests you to renovate all of your package.json dependencies up-to-date. You should preserve the settings clarified in package.json.

• Third,

If you're working on ubuntu or OS X, you won't face this issue, I guess.

---

PS:

According to your reply, I'd like to think about the workaround.

• Remove the local node_modules & package-lock.json
• Clean npm cache by npm cache verify
• Update the global npm by sudo npm i -g npm
• Reinstall the local node_modules by npm i

Hope this might help.

Answer 2

I found a solution, this is what I did:

Open your package-lock.json.

Find node_modules/fsevents, inside this there is something called "os", I had only this:

 "os": [
        "darwin",
      ],

So my OS is windows 10 64 bits I just added my OS inside "os", the result is this:

 "os": [
        "darwin",
        "win32"
      ],

then save and is solved, after doing this I could install the package I was trying to install that I couldn't.

Answer 3

As I got into the issue just today I read the first solution but tried one thing first

Remove package-lock.json and node_modules dir first

Run these commands and it should work.

rm -rf node_modules package-lock.json
npm install

worked like a charm maybe it'll help someone else.

Answer 4

When seeing this kind of message on ionic or anywhere else, do run npm audit fix and see if you can successfully follow the given advice to resolve all "high severity vulnerability" issues and contribute the resulting updated dependencies back to the given codebase.

What's happening here is that a package called chokidar is being used to "watch" filesystem directories for "events" (like files being added). chokidar is a wrapper for Linux-, Windows-, and Mac-specific filesystem-watching packages, of which fsevents is the Mac variant. So, I am pretty sure anything that uses chokidar is going to have fsevents as an optional dependency, but as others have said, this WARN message can be safely ignored, as chokidar supports all common desktop architectures.

Answer 5

If like me, you got this issue because of using two different package managers at the same time (E.g. yarn and npm), you can simply remove the lockfile and rerun your package manager.

rm package-lock.json

The lockfile will be regenerated the next time you run your package manager. I got this error while trying to upgrade the packages with npm upgrade. After deleting the lockfile, upgrade proceeded smoothly and the lockfile was created correctly.

Answer 6

This warning will appear if you added IOS as platform to your project and run npm i on Windows or Linux. As you can't build IOS packages on these systems anyway you can safely ignore this warning.

Answer 7

I had the same issue:

1. Deleted package-lock.json
2. npm install

viola, it worked for me

Answer 8

After opening the command prompt or PowerShell in the administrator mode, what helped me was following this answer here.

I ran the command: npm i --force and that seemed to fix the issue.

Answer 9

If you're seeing this error in a node Github workflow, you can update the runs-on value in node.js.yml to macos-latest and it will work. Worked for me anyways.

Answer 10

The critical breakthrough for me was actually simple:

yarn remove fsevents

I verified that it worked by ctrl + f in yarn.lock for 'fsevents'. Before removing it, it appeared 9 times, after removing it, only 8. So I knew it had some effect.

Extra info

After removing fsevents:

git add .
git commit -m "Removed fsevents"
git push heroku master

and it worked.

---

Note that I also had to run bin/webpack-dev-server to see if the assets would precompile (better to try this locally where you can quickly address any deficiencies, rather than on heroku where it will take time to build).

I fixed any missing libraries with something like yarn add '@rails/activestorage' '@rails/ujs' etc, and when the app went to heroku it worked.

Answer 11

npm i work on dev machine, but fail on the CI pipeline.

The problem was the package-lock.json format version. On my dev machine, I have a most recent version of npm that on the CI machine. The recent npm version has generated a package-lock.json with lockfileVersion at 2 :

{
  "name": "MyAwesomeProject",
  "version": "1.0.0",
  "lockfileVersion": 2,
  "requires": true,
  "packages": {
    ...
  }
}

I removed package-lock.json from my repository and build CI worked.

Answer 12

I had to add webpack: ^5.87.0 to devDependencies in package.json. Then delete node_modules and package-lock.json, and in case npm cache clean --force and finally the npm install.

if you crawl up the package-lock.json, the module chain is as follows: fsevents => chokidar => watchpack => webpack. I did not need to add win32 to the arch targets

Answer 13

Try upgrading the node version to 8.5.0. Version >=8 suppresses this issue.

Answer 14

You have to add win64 on package.json file

For example

{"os":"darwin,linux","arch":"any"} will replace with

{"os":"darwin,linux,win32,win64","arch":"any"}