-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
RangeError Maximum call stack size exceeded on nodejs v17.9.0 #44913
Comments
Node.js 17.9.0 is unsupported as of 4 months ago. Please update to 18.x. Running your code sample on the latest 18.x release (as well as the latest 16.x release), I get this error: |
(Closed in the hopes that this is fixed and not a bug in Node.js, but if I'm wrong about that, please comment or re-open. Thanks!) |
Sorry about that. I've done a miniature edit to the snippet before submitting, and forget to rename this part too.
I did install another version i.e. v18.9.1, and it worked. I was wondering if the docs mention such facts i.e. the schedule of the support cycle, and 'unstable' releases. |
We might want to improve the wording, but there's a fairly prominent link on the home page of the nodejs.org website that says Long Term Support (LTS) schedule but it's really the full support schedule. (Scroll down for unsupported releases to see when they went in and out of support.) Even numbered releases (14, 16, 18, etc.) are supported for much longer than odd numbered releases (which are only supported for around 8 months or something like that). |
Version
17.9.0
Platform
Linux laptop 5.15.0-48-generic #54~20.04.1-Ubuntu SMP Thu Sep 1 16:17:26 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
N/A
What steps will reproduce the bug?
Run the following code snippet with nodejs version
17.9.0
How often does it reproduce? Is there a required condition?
Always.
Can't seem to get what that means
What is the expected behavior?
The abort signal terminates the open interface, without any raised exceptions.
What do you see instead?
Additional information
No response
The text was updated successfully, but these errors were encountered: