fsevents optional dependency returns not compatible with system

babeljs fsevents
logos_164 picture logos_164 · May 27, 2018 · Viewed 8k times · Source

Iam installing babel core 6.26.0 per this documentation, everything goes smoothly except for the following error:

npm WARN optional Skipping failed optional dependency /babel-cli/chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: [email protected]
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: [email protected]

I'm wondering if this is just noise? Or if there is a workaround someone might know of? I've seen some documentation around it but nothing concrete.

Answer

loganfsmyth picture loganfsmyth · May 27, 2018

Yes, this is expected. fsevents is only supported on OSX, so on any other system you'll see a message that it has been skipped.

Related questions

Using Node.js require vs. ES6 import/export

In a project I'm collaborating on, we have two choices on which module system we can use: Importing modules using require, and exporting using module.exports and exports.foo. Importing modules using ES6 import, and exporting using ES6 export Are …

Read More
Babel 6 regeneratorRuntime is not defined

I'm trying to use async, await from scratch on Babel 6, but I'm getting regeneratorRuntime is not defined. .babelrc file { "presets": [ "es2015", "stage-0" ] } package.json file "devDependencies": { "babel-core": "^6.0.20", "babel-preset-es2015": "^6.0.15", "babel-preset-stage-0": "^6.0.15" } .js file "use strict"; async function foo() { await bar(); } function bar() { } …

Read More
Getting Unexpected Token Export

I am trying to run some ES6 code in my project but I am getting an unexpected token export error. export class MyClass { constructor() { console.log("es6"); } }

Read More