-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
fix(engines): syncpack 12.x supports node >=18 not >=16 #215
Comments
Thanks a lot @350str, I'll bump |
sure, v11 works great for me, thanks! |
Yikes, and here I am on Node 16, needing |
https://github.com/JamieMason/syncpack/releases/tag/14.0.0-alpha.1 might work if you want to try it @lkraav |
Tyvm, that does seem to take care of the engine problem. But I see new syncpack does a lot of things very differently. I'd expect |
Can you summarise what you were wanting to do please @lkraav? To find and fix something specific by the sound of it? |
Certainly. I was looking to take control of very limited amount of package globs at a time. It's unclear from alpha release notes if syncpack-14 even supports Beyond that, I would've wanted to run |
Thanks this is helpful.
Config file loading and filenames are the same as before, some config values have changed a little though - I need to write a lot of docs very soon. --filter is replaced by --dependencies, you can see some examples here
I changed filtering to only apply to linting in 14-alpha but this has changed my mind, I'll put that back in the fix command so you can do this |
Description
Hello. I found a problem, syncpack v12 doesn't work with node v16, because packages globby v14+ and ora v8+ require node v18+
Suggested Solution
update engines field in package.json for correct node version (>18) or downgrade major version of this packages in deps
The text was updated successfully, but these errors were encountered: