Node 16 support
See original GitHub issueWhen starting the emulator on NodeJS 16 there is an error thrown when initializing the app.
(node:31765) UnhandledPromiseRejectionWarning: Error: Credential implementation provided to initializeApp() via the "credential" property failed to fetch a valid Google OAuth2 access token with the following error: "Error fetching access token: Error while making request: getaddrinfo ENOTFOUND metadata.google.internal. Error code: ENOTFOUND".
This occurs when using an emulator start script with the following:
const admin = require('firebase-admin')
admin.initializeApp()
Should node 16 be working when starting the emulator?
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Node.js - endoflife.date
Release Released Active Support
19 2 months and 6 days ago. (18 Oct 2022) Ends in 3 months and 1 week. (01 Apr 2...
18...
Read more >Bringing forward the End-of-Life Date for Node.js 16
We are moving the End-of-Life date of Node.js 16 by seven months to coincide with the end of support of OpenSSL 1.1.1 on...
Read more >Node.js Release Working Group - GitHub
There are three phases that a Node.js release can be in: 'Current', 'Active Long Term Support (LTS)', and 'Maintenance'. Odd-numbered release lines are...
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 >Supported Node versions - Node-RED
Node -RED currently recommends Node 16.x LTS. Version, Support Level, Notes ... Our goal is to support the Maintenance and Active LTS releases....
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
@Joebayld as a workaround you can force emulators to use another node version with the following
npx
command:(in the example above with node version 14.16, the same as the beta one used by functions, to avoid deployment surprises 😉 )
Closing due to inactivity. We can reopen later if you still run into this issue on the latest
firebase-admin
version.