question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Update extensions to Node 10

See original GitHub issue

[READ] Step 1: Are you in the right place?

Issues filed here should be about a feature request for a specific extension in this repository. To file a feature request that affects multiple extensions or the Firebase Extensions platform, please reach out to Firebase support directly.

[REQUIRED] Step 2: Extension name

This feature request is for extension: firestore-bigquery-export

What feature would you like to see?

Please add support for the Node 10 runtime environment, now that it reached GA, and the Node 8 environment will be deprecated.

See this email we recently got:

The Node.js 10 runtime on Cloud Function has now reached General Availability and the Node.js 8 runtime on Cloud Functions will be deprecated. To avoid potential disruptions or security risks, you should update your functions to Node.js 10.

How would you use it?

Tell us how you’d use this feature in your app.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:9
  • Comments:7 (3 by maintainers)

github_iconTop GitHub Comments

10reactions
mbleighcommented, Jun 18, 2020

Hi folks, just wanted to give a little context here. If it were a simple technical matter of “upgrade to Node 10” we’d have already done it as soon as Node 10 went GA.

However, because of the billing changes that are coming soon for Node 10 (requiring a Blaze plan), we need to be careful in how we migrate extensions that currently work on the Spark plan. This is a high-priority item for the team, but again one that requires some care to address.

I am going to raise the idea of migrating extensions that already require a billing account (due to external network calls or integrations with billing-required GCP services) as that might be more straightforward. You can consider this the public issue tracker for migrating extensions to Node 10, we’ll keep communicating on here.

1reaction
thatfiredevcommented, Aug 2, 2020

Can we pin this issue to the issues page? It might be helpful to prevent newcomers from opening new issues with the same suggestion.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to update your Node.js dependencies [10 of 26]
How to update your Node.js dependencies [10 of 26] ... Packages gets updated constantly, with new features, bug fixes or security patches.
Read more >
Update NodeJS extension to support Node 10, 11, 12
I'have a node application that needs the version 10 of NodeJS. An update to this extension wouldn't be bad.
Read more >
Native Extensions for Node.js - Medium
In this article we will talk about the most important concepts to develop native extensions for Node.js. Later, I will show how to...
Read more >
Download & Update Node.js to the Latest Version! Node v19 ...
Direct download links to update to the latest Node.js versions: Node v19.0.0 / LTS v16.18.0.
Read more >
Issue - How to update Node.js to newest version? - Plesk Forum
js extension" (1.4.0-127) installed, however the node.js version is outdated (v12.4.0). when running "npm run dev" for ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found