Node 10 support about azure-functions-nodejs-worker HOT 6 CLOSED

We want to update to (at least) [email protected] and [email protected]

Blocked by issue in grpc-node
There's an error in grpc's index.d.ts file that keeps us from being able to use [email protected] in the same project: grpc/grpc-node#176

from azure-functions-nodejs-worker.

why is this breaking? Does it mean we will drop node 8?

from azure-functions-nodejs-worker.

I don't think we've decided whether or not we're keeping node 8 as a backup (likely yes? @paulbatum), but we definitely will be changing the default version to 10

from azure-functions-nodejs-worker.

thanks @mhoeger I was asking in the context of the email thread about handling WEBSITE_NODE_DEFAULT_VERSION, I'll respond on that thread

from azure-functions-nodejs-worker.

Since V2 is still in beta, my preference is to only support node 10 i.e. V2 apps would be set to node 10, we would emit a warning if a different version was detected, our test coverage would be on node 10, etc. We can do all this without deliberately blocking node 8. At least this way we are able to postpone engineering challenges implicit in supporting multiple node versions (such as doing test runs against multiple versions).

from azure-functions-nodejs-worker.

re-opening to track pulling to functions-host repo

from azure-functions-nodejs-worker.