[node] v12 support

[tay1orjones]

Summary

We have not tested if the codebase builds properly with Node v12. This needs to be validated.

• update .nvmrc to 12
• add engines field to package.json as a best practice, specify 12.x
• update any required dependencies to ensure the build and Travis CI aren't interrupted
• update any documentation that specifies the previous 10.15.3 version from [node] specify v10 and document #735
• ensure the runtimeVersion is updated in ./.vscode/launch.json

_{Internal issue #62}

[tay1orjones]

Node release schedule for reference

Major Node.js versions enter Current release status for six months, which gives library authors time to add support for them. After six months, odd-numbered releases (9, 11, etc.) become unsupported, and even-numbered releases (10, 12, etc.) move to Active LTS status and are ready for general use. LTS release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months. Production applications should only use Active LTS or Maintenance LTS releases.

[tay1orjones]

This will bring us in line with Carbon, they updated in carbon-design-system/carbon#5391

[tay1orjones]

I believe this will fix the node warning we see in the console when running the test suite

(node:41998) ExperimentalWarning: The fs.promises API is experimental

[tay1orjones]

🎉 This issue has been resolved in version 2.82.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀