Migrate from Travis CI to Github Actions

[Jooms]

This resolves some of the tasks in #19

• Add a GitHub Action workflow to verify a successful build of the project. Should be triggered by all pull requests.

Note:
I had trouble figuring out how to just build a node project. It seems that since Javascript is interpreted (rather than compiled), all we can do is run it. So I added a flag to the starting file that short-circuits the code just before the server starts (and tries to connect to other things).

If there are better ideas, let me know.

[Jooms]

@kbuffardi I don't see an option on my end yet, but I'm assuming you can please squash + merge this. If not, please let me clean up the commits before merging.

[jayrevolinskyjr]

Is there a way to guarantee that static analysis occurs separate from the start-and-kill?

My only concern is that it might try to run the build and analysis together. I believe that's the case but I am uncertain. Despite this, LGTM.

[Jooms]

Is there a way to guarantee that static analysis occurs separate from the start-and-kill?

My only concern is that it might try to run the build and analysis together. I believe that's the case but I am uncertain. Despite this, LGTM.

Great question.

Just a clarification.
The npm ci here is just clean install the project. It's an alternative to npm install that is meant to run in pipelines because it adds a small amount of extra validation for third-party dependencies. https://docs.npmjs.com/cli/v9/commands/npm-ci

So in this case, we're doing a little bit of static analysis of the dependencies, but often if those are broken the build will fail. So I'd argue it makes sense in this case.

[reembot]

LGMT outside of the .yml filename. If we're expecting multiple workflow yamls, naming this something specific to its purpose could be helpful?

[reembot]

LGTM

[Jooms]

Ugh sorry for the commit spam. I thought I selected squash merge