-
-
Notifications
You must be signed in to change notification settings - Fork 54
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
v12.4.0 is broken on Node 18 #237
Comments
Thanks @ColinCee, |
Thanks Jamie, very interesting that pnpm is passing whilst yarn isn't. Note the project I'm working on is using yarn v1 which I know is not ideal |
It's all good, a lot of people still use Yarn v1 – I still have it on a lot of projects. |
Closes #237 BREAKING CHANGE: Changed `engines.node` from `>=16` to `>=18.18.0`. `minimatch@10` was updated in `[email protected]` which required `node@>=20` and caused issues in some projects. This change adds a local linter to verify that the node engines of syncpack's dependencies all satisfy syncpack's own node engine. Using this linter found that the minimum node engine of all of syncpack's dependencies is v18.18.0.
Hopefully fixed in 13.0.0 |
Description
yarn install syncpack
error [email protected]: The engine "node" is incompatible with this module. Expected version "20 || >=22". Got "18.19.0"
Suggested Solution
The text was updated successfully, but these errors were encountered: