Update travis config

[jsumners]

No description provided.

[UziTech]

Might be better to use lts/* and node so they don't have to be updated on every new node release.

[UziTech]

even better use jobs

sudo: false

language: node_js

git:
  depth: 3

branches:
  only:
  - master
  - next

jobs:
  include:
    - stage: test 👩🏽‍💻
      script: npm test
      node_js: node
    - node_js: lts/*

    - stage: lint ✨
      script: npm run lint
      node_js: lts/*

[UziTech]

It would be great to have windows tests too

appveyor.yml:

# Test against the latest version of this Node.js version
environment:
  matrix:
    # node.js
    - nodejs_version: "lts"
    - nodejs_version: "stable"

# Install scripts. (runs after repo cloning)
install:
  # Get the latest stable version of Node.js or io.js
  - ps: Install-Product node $env:nodejs_version
  # install modules
  - npm install

# Post-install test scripts.
test_script:
  # Output useful info for debugging.
  - node --version
  - npm --version
  # run tests
  - npm test

# Don't actually build.
build: off

[jsumners]

I had too bad of an experience with AppVeyor when we had it setup on the Fastify org. I have no intention of using that service. I am still waiting to hear from @github about getting Actions enabled for this organization. If that comes through, I intend to switch over to it. For now, I just want to get some basic CI going so we can more easily audit these PRs.

[UziTech]

I haven't had great luck with windows on travis. It has been in beta for a few years and it doesn't look like they are working on it too hard.

[jsumners]

🤷‍♂️ this config seems to be running the lts/* tests twice, but I'm merging it. I want to move on to linting.

[jsumners]

⚠️ This issue has been locked due to age. If you have encountered a recent
problem that seems to be covered by this issue, please open a new issue.

Please include a minimal reproducible example
when opening a new issue.