Node.js 12 support?
See original GitHub issueIt seems as part of https://github.com/nodejs/undici/pull/1604, Node.js 12 was removed from the support matrix - not sure if that was intentional?
If Node.js 12 is no longer supported - then probably the engines
field needs to be updated (incl. a major version release) - but quite possibly that was a typo and the matrix needs to be adjusted?
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Node.js - endoflife.date
Release Released Active Support Se...
19 2 months and 1 week ago. (18 Oct 2022) Ends in 3 months. (01 Apr 2023) En...
18 (...
Read more >Node v12.22.12 (LTS)
js 12 release. Node.js 12 will reach End-of-Life status on 30 April 2022, after which it will no receive updates. You are strongly...
Read more >Announcing the end of support for Node.js 12.x in the AWS ...
Starting November 1, 2022, AWS SDK For JavaScript (v3) will no longer support Node.js 12.x which was EOL on April 30, 2022.
Read more >Node.js Release Working Group - GitHub
Following those 12 months of active support, the major version will transition into "maintenance" mode for 18 months. Prior to Node.js 12 the...
Read more >Node.js ES2015/ES6, ES2016 and ES2017 support
Yes. Yes Yes. Yes Error. Error Error. Error Error. Error Error. Error
function() function() function() function() function() function()
function() function() function() function() function() function()
function() function()...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Seems there’s a test failing (
test/request-timeout.js
) - I can take a look later.Updated the PR, also had to disable
jest
for Node 12 - seems that it’s accumulating the disabled tests - not sure if that’s becoming problematic or not just yet?