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
Node 16.13 (LTS) Support #9698
Comments
See #9694 |
Yes, i saw it. it remove the warning saying node 16 is not tested, but i don't think it add support |
@Thomasevano I happened to dig into this just last night! As far as I can tell there are certain dependencies using a very ancient version of workerpool. In the case of my app there are two offenders:
|
Oh ok, maybe you right, i didn't think of this, cause the error happened in |
Hi all! 👋 this is something that I'd love to get working -- I have an M1 that doesn't like Node 14 at all 😬 |
so this should be fixed since we backported the fix to the "very ancient version of workerpool" https://github.com/josdejong/workerpool/releases/tag/v2.3.4 You might have a lock file that is preventing you from getting that patch release but if you just update that should be fine (with npm the command is just |
I notice that as of ember-cli 3.28 we get this warning despite node 16 being the active LTS both then (at time of ember-cli release) and now:
|
Thank you @mansona! Upgrading |
The original issue has been fixed. Thanks for the discussion! |
@locks can you open a new ticket then for adding node16 support to ember-cli? |
@runspired node 16 has been added to the CI matrix and I just tested running an app and didn't have any problems. Can you open the ticket with a reprodduction if you're still having problems? |
Hello,
We want to upgrade our app to Node 16.13 but when we start the application, we encounter the following issue:
TypeError [ERR_INVALID_ARG_TYPE]: The "options" argument must be of type object. Received an instance of Array
Is Node 16 support in the roadmap ?
Output from
ember version --verbose && npm --version && yarn --version
:The text was updated successfully, but these errors were encountered: