chokidar throws "Can't resolve 'fsevents'" warning on Windows

[vinceau]

After the #45 PR was merged, on Windows machines it will still try to import fsevents despite not being supported. This seems to not impact the building of the binary using yarn run dist but seems to halt yarn run start.

The stack trace of the warning message is as follows:

        WARNING in ./node_modules/@vinceau/slp-realtime/node_modules/chokidar/lib/fsevents-handler.js
        Module not found: Error: Can't resolve 'fsevents' in 'D:\a\project-clippi\project-clippi\node_modules\@vinceau\slp-realtime\node_modules\chokidar\lib'
         @ ./node_modules/@vinceau/slp-realtime/node_modules/chokidar/lib/fsevents-handler.js
         @ ./node_modules/@vinceau/slp-realtime/node_modules/chokidar/index.js
         @ ./node_modules/@vinceau/slp-realtime/dist/index.es.js
         @ ./src/common/fileProcessor.ts
         @ ./node_modules/ts-loader??ref--13-0!./src/common/workers/fileProcessor.worker.ts

A workaround for the issue is to delete lines 8-12 from the node_modules/@vinceau/slp-realtime/node_modules/chokidar/lib/fsevents-handler.js.

try {
  fsevents = require('fsevents');
} catch (error) {
  if (process.env.CHOKIDAR_PRINT_FSEVENTS_REQUIRE_ERROR) console.error(error);
}

Not really sure how to fix this since the error is happening from the actual require() statement and not coming from the catch and subsequent console.error().

This issue only affects Windows.

[totymedli]

There is an issue on Chokidar's repo for the same problem. Over there I explained a solution. It is still kind of a workaround, but you don't need to change a 3rd party dependency's code:

Just mock the fsevents module then create an alias for it so webpack can resolve the require:

fsevents.js:

module.exports = undefined

In webpack.config.js:

resolve: {
  alias: {
    fsevents$: path.resolve(__dirname, `fsevents.js`),
  },
},

I explain this in detail on Stack Overflow

[vinceau]

Thanks for your comment. You've inspired a fix which does not break fsevents on MacOS which your solution unfortunately does. See below or 5bda5f0.

Simply add this to the webpack.config.js file.

  if (process.platform !== "darwin") {
    context.plugins.push(
      new webpack.IgnorePlugin({
        resourceRegExp: /^fsevents$/,
      })
    );
  }