Update package.json to install fsevents on node >= 12

[yashLadha]

Summary

When executing the command yarn install in the project root directory using node 12. It breaks because fsevents exits with code 1. There is already an issue on node repo which resolves this stated in this comment

Other Information

Closes #38612

[yashLadha]

Need to pass --no-optional in docker file so that optional dependencies doesn't get installed

[eugeneius]

It looks like adding a resolution prevents optional dependencies from being ignored when they can't be installed on the current system:

https://buildkite.com/rails/rails/builds/67339#654dc08d-e7ab-44bb-9936-ad6a725a1ce7/1512-1516

error fsevents@1.2.11: The platform "linux" is incompatible with this module.
error Found incompatible module.

Here's what happens on master, with no resolution:

https://buildkite.com/rails/rails/builds/67326#872684c5-29d4-46f9-8ade-99e4098e8c09/224-236

info fsevents@1.2.11: The platform "linux" is incompatible with this module.
info "fsevents@1.2.11" is an optional dependency and failed compatibility check. Excluding it from installation.

That difference in behaviour is a bug in Yarn, tracked here: yarnpkg/yarn#7590

I think we can work around it by adding the resolution, running yarn install (on a Mac), committing the updated yarn.lock and throwing away the changes to package.json.

[eugeneius]

I don't think we should fix the problem by passing --no-optional when running Yarn on CI, since it would force contributors installing dependencies locally on Linux or Windows to also use the flag.

[yashLadha]

Did as suggested @eugeneius

[eugeneius]

Thanks @yashLadha! This looks good to me.

I can confirm that on master running yarn install on macOS with Node 12.16.0 fails to compile the fsevents package as described in #38612, but with this change the package is compiled successfully.

[yashLadha]

@eugeneius Can this be merged?