yarn 1.22.5
I update packages every day with this command:
yarn upgrade
But today I got a problem.
As before, I tried to update packages. I ran the command I showed above. As a result, I got this:
warning "webpack-dev-server > [email protected]" has unmet peer dependency "webpack@^4.0.0".
[4/4] 🔨 Building fresh packages...
[1/5] ⠂ @popperjs/core
[2/5] ⠂ fsevents
[3/5] ⠂ core-js
[4/5] ⠂ node-sass
error /Users/afuno/app1/node_modules/@popperjs/core: Command failed.
Exit code: 127
Command: patch-package
Arguments:
Directory: /Users/afuno/app1/node_modules/@popperjs/core
I deleted the yarn.lock file and node_modules directory. And then I ran this command:
yarn install
And it didn't help.
I deleted the @popperjs/core line from the package.json file. And yarn started to install and update successfully.
Then I tried to execute this command:
yarn add @popperjs/core
And got the error:
[4/4] 🔨 Building fresh packages...
error /Users/afuno/app1/node_modules/@popperjs/core: Command failed.
Exit code: 127
Command: patch-package
Arguments:
Directory: /Users/afuno/app1/node_modules/@popperjs/core
Output:
/bin/sh: patch-package: command not found
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
Got the same error here
I saw that you made a new release 30 minutes ago. The problem is related to this release. Using fixed version 2.4.4 is successful.
To everyone who gets this error, I recommend temporarily committing version 2.4.4 in the package.json file:
"@popperjs/core": "2.4.4",
Same here: v2.5.0 is breaking the install-process. Fresh node-project, directly after npm init (latest LTS):
❯ npm install @popperjs/core
> @popperjs/[email protected] postinstall ~/Downloads/poppertest/node_modules/@popperjs/core
> patch-package
sh: patch-package: command not found
npm WARN [email protected] No description
npm WARN [email protected] No repository field.
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! @popperjs/[email protected] postinstall: `patch-package`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the @popperjs/[email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2.5.1 should fix it, it will be available in a few minutes
@FezVrasta Thank you for your prompt work
May someone confirm it's working?
@FezVrasta In version 2.5.1 everything is successful.
Most helpful comment
2.5.1 should fix it, it will be available in a few minutes