-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to update mocha to 8.3.1: fsevents@patch - Cannot apply hunk #1 #4602
Comments
@DJ-Glock I also use Windows 10 and the installation with NPM runs successfully. I just get the warning:
I have no idea why it doesn't work with Yarn. Doing some googling I get the impression it's a Yarn issue. |
maybe something like: |
@juergba you might be right about optional. It looks like the chain is: mocha requires chokidar and chokidar requires fsevents, but optionally. I have no idea why yarn 2 tries to install optional dependency and flag --ignore-optional does not work as per this issue. Thanks. |
Update: it was a yarn issue. It looks like issue was fixed in yarn 2.4.1. We updated yarn to 2.4.0 - issue was in place, but after ipdating yarn to 2.4.1 everything is fine. Hope this will help someone. |
Prerequisites
faq
labelnode node_modules/.bin/mocha --version
(Local) andmocha --version
(Global). We recommend that you not install Mocha globally.Description
I'm trying to update mocha from version 8.2.1 to 8.3.1. Mocha is installed as dev dependency.
Steps to Reproduce
Set version 8.3.1 in package.json and run yarn or use upgrade-interactive or use yarn add mocha --dev.
Expected behavior:
Mocha 8.3.1 should be installed.
Actual behavior: [What actually happens]
Error occurred:
➤ YN0066: │ fsevents@patch:fsevents@npm%3A2.3.2#builtin<compat/fsevents>::version=2.3.2&hash=127e8e: Cannot apply hunk #1 (set enableInlineHunks for details)
Versions
mocha --version
andnode node_modules/.bin/mocha --version
: 8.2.1node --version
: 12.18.3I searched for this error and found many issues from 2020, but all of them were resolved somehow. So not sure why it occurred for me especially on Windows.
The text was updated successfully, but these errors were encountered: