Update Node to use LTS, update engine requirement in package.json

Feature Request

Description

It is proposed that instead of locking down to a specific Node version in the .nvmrc, we should be pointing to use the LTS.

As of nvm v0.33.6 nvm supports the use of lts/* for long term support in the .nvmrc config file.

You can reference LTS versions in aliases and .nvmrc files with the notation lts/* for the latest LTS

This way we don’t have to worry about manually updating the Node version and we will always target LTS Node.

# .nvmrc
lts/*

It is proposed to update the engine requirement to use both Node v8.x and v10.x.

The new Node LTS version is 10.x which causes issues with Terra since it’s still on 8.x (now in maintenance).

# package.json
"engines": {
  "node": "^8 || ^10"
}

Additional Context / Screenshots

[bjankord]

lts/carbon sounds fine to me. Does setting ^8.9.2 in the .nvmrc file do the same thing? That caret syntax may be an npm only thing that nvm doesn’t parse.

Edit: Tried running nvm install ^8.9.2 to see if it would install latest 8.x version, didn’t work.

I’m cool with setting lts/carbon in the .nvmrc file and switching it to lts/dubnium when we update to node 10.x along with updating our node engine key in package.json to "node" : ">=8.9.2"

[dev-cprice]

How about instead of lts/*, we lock it down to 8.x at least? If we do lts/carbon it will pull in all minor & patch versions of 8.x carbon