-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Move to Node 18 #6396
Comments
So because of this change with the way JSON files are imported in Node 16, every package plus Reaction itself is going to need to be updated in a way that is backwards compatible. Not a lot of programming work, but a fair amount of busy work. That is not necessarily the only change that needs to be made, but the first one I have identified |
@zenweasel
This currently prevents me to use @reactioncommerce/api-core with Node 16 in a fresh project. I still need to fallback to Node 14. I would really like to have this issue resolved and could offer my support, if required. |
We may want to look at just jumping to Node 18 since that just became LTS |
That would be great. Since nothing works on Macbooks with M1. |
Changing this to Node 18, since going to 16 only buys us 5 more months |
any update on this? |
There's a pr on all of the repos that's just waiting for review |
Node 18 is LTS. Let's try to get on top of this. Hopefully not many breaking changes if any.
The text was updated successfully, but these errors were encountered: