Node 16.13 (LTS) Support
See original GitHub issueHello,
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
:
ember-cli: 3.28.4
node: 16.13.0
v8: 9.4.146.19-node.13
uv: 1.42.0
zlib: 1.2.11
brotli: 1.0.9
ares: 1.17.2
modules: 93
nghttp2: 1.45.1
napi: 8
llhttp: 6.0.4
openssl: 1.1.1l+quic
cldr: 39.0
icu: 69.1
tz: 2021a
unicode: 13.0
ngtcp2: 0.1.0-DEV
nghttp3: 0.1.0-DEV
os: darwin x64
8.1.0
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Node v16.13.0 (LTS)
This release marks the transition of Node.js 16.x into Long Term Support (LTS) with the codename 'Gallium'. The 16.x release line now moves ......
Read more >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 >Support node 16.13+ (Official LTS release) · Issue #634 - GitHub
The latest release supported by Azure Static Web Apps Github Action is 16.8.0. Are there any plans to upgrade the Github action to...
Read more >Download Node.js
Download the Node.js source code, a pre-built installer for your platform, ... LTS release status is "long-term support", which typically guarantees that ...
Read more >Node 16.13.2 (Current LTS) on Azure App Services
I want to use the latest LTS of Node 16 for my Linux App Service on Azure but the only LTS version that...
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
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
npm update workerpool
and that will update the lockfile accordingly if you’re on the latest npm)Hi all! 👋 this is something that I’d love to get working – I have an M1 that doesn’t like Node 14 at all 😬