Update to node@16 and npm@8

[deleonn]

Description

Makes the required changes so the library works with node@16x and npm@8.x. This PR also migrates from TravisCI to CircleCI and introduces the same automatic publishing flow as mongoose-models.

How to Test

1. Pull the branch: feature/sc-102555/update-particle-api-js-to-node-js-v16-and
2. Update your local node version to v16.x and npm to version to v8.x. Use nvm use 16 or equivalent.
3. Verify your updates: node -v && npm -v
4. Install dependencies: npm i
5. Run the tests npm run test

Outcome
All tests should pass. npm i should run without issues.

Related / Discussions

• https://app.shortcut.com/particle/story/102555/update-particle-api-js-to-node-js-v16-and-npm-v8

Completeness

• PR opened 🎉
• Testing instructions have been provided
• Tracking story is up to date (tasks are marked complete, state is "ready for review")
• Docs have been updated
• Branch is rebased against target (typically main)

[hugomontero]

👍

[busticated]

@deleonn i see this in the CI logs for the test step:

{
  error: Error: connect ECONNREFUSED 127.0.0.1:9090
      at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16) {
    errno: -111,
    code: 'ECONNREFUSED',
    syscall: 'connect',
    address: '127.0.0.1',
    port: 9090
  },
  errorDescription: 'Network error from http://localhost:9090/v1/devices/events'
}

any ideas?

[busticated]

this can go away i think

[busticated]

ok, i created a record in 1Password w/ the required API credentials. Pull those into CircleCI (make sure they are hidden from public view as this is a public repo) and wire up the node-side tests.

i don't think you need to run the browser tests across multiple versions of node since the runtime in that case is the browser itself and it will always be the same (at least as it is currently configured).

ideally, we'd run the node-side tests across multiple versions of node but the brower-side tests in a single version (presumably node@16)