Node 10 support

[mhoeger]

Although Node 8 is under long-term support, Node 9 is current. Any install via brew or chocolatey will default to Node 9, which creates a bad experience for local developers that install node for the first time on a machine and must downgrade to 8.

UPDATE: node 10 just released

[mhoeger]

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

[ahmelsayed]

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

[mhoeger]

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

[ahmelsayed]

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

[paulbatum]

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).

[mhoeger]

re-opening to track pulling to functions-host repo