chore: update fsevents

[cmdcarini]

Summary

Attempts to address Jest hanging on test execution when running on macOS by updating the nested optional fsevents dependency in the jest-haste-map module to include upstream changes that resolved the underlying issue.

Test plan

When running latest stable version of Jest (v26.6.3), manually overriding downstream dependency fsevents to v2.2.1 by doing the following, resolves hang up issues, and maintains Jest functionality.

npm i -D fsevents@2.2.1
npm dedupe
npm uninstall -D fsevents

[facebook-github-bot]

Hi @cmdcarini!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

[merceyz]

Semver already takes care of this bump for users so this shouldn't be needed unless it's an issue in this repo as well, left some comments inline either way

[merceyz]

Need to run yarn to update the lockfile

[cmdcarini]

Should (hopefully) be done!

[merceyz]

Seems like you used Yarn 1 to do that instead of the checked in version, how old is your Yarn 1 version since it didn't pick up on the yarn-path setting?

[SimenB]

@merceyz I tried to fix it, but the patch in yarn v2 seems broken.

➤ YN0066: │ fsevents@patch:fsevents@npm%3A2.3.1#builtin<compat/fsevents>::version=2.3.1&hash=127e8e: Cannot apply hunk #1
➤ YN0000: │     }
➤ YN0000: │
➤ YN0028: │ -   let instance = Native.start(path, handler);
➤ YN0028: │ +   let VFS = require('./vfs');
➤ YN0028: │ +   let vfs = new VFS(path);
➤ YN0028: │ +   let instance = Native.start(vfs.resolvedPath, vfs.wrap(handler));
➤ YN0000: │     if (!instance) throw new Error(`could not watch: ${path}`);
➤ YN0000: │     return () => {

(same for 2.2.1, fwiw)

[merceyz]

That was fixed in yarnpkg/berry#2078 (yarn set version latest)

[SimenB]

Oh, the fork was super outdated (over 120 commits behind) and had an old version of yarn. Merging in master fixed the issue 👍

[SimenB]

Thanks @cmdcarini!

[arnulfojr]

Hi, do you have a release date for this?
Can we have maybe 26.6.4, instead of waiting for v27?
The jest tests keep hanging with the current version of fsevents

[SimenB]

You don't need it, latest version is in semver range. just delete the entry from you lockfile

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.