* Create testing framework for CLI
- Need to add tsconfig for specs to convert module format and add spec
dir to output
- Use jasmine-ts to test
expected dev cycle would be to have two watchers, one for jslib
and one for CLI tests. We could add jslib tests to this jasmine config,
but it feels wrong to test a submodule
* Run prettier
* Add tests to build pipeline
* Include required package
* Add placeholder test
* Run prettier
* Add nodemon and fix watch
* Pull in jslib
* Bump engines required to node 16 and npm 8
* Bump @types/node to 16
* Modify build.yml to build with node 16 and npm 8
* Update requirements in README.md
* Update 'setup-node' action version
* Update 'pkg' to 5.5.1
* Removed installation of npm8
npm8 is included in node v16
* Pull jslib
* Change engines to only warn on node < 16
Co-authored-by: Vince Grassia <593223+vgrassia@users.noreply.github.com>
* Removing branch constraints on when to expose build assets
* updating to snap 5.0
* adding more snapcraft 5.0 specific updates
* installing multipass
* fixing syntax error
* switching from using a VM via multipass to using lxd
* trying the official snap build actions
* fixing error
* commenting out the snapcraft version
* testing the new changes to the snapcraft.yml file
* nameing the build snap task
* naming the build snap task
* fixing the resource hacker hash checking issue
* updating package command
* updating the release workflow to match the build workflow. Removing the unneeded env var
* fixing some formatting
* Update dependencies
* Remove types which are no longer needed
* Bump jslib
* Revert pkg to 4.5.1 since 5.0.0 does not compile on linux.
* Bump pkg-fetch in build pipeline
* testing new fix
* adding this branch to the snap portion of the test
* adding in the build artifact for the linux executable
* removing the path since GitHub is being dumb...
* adding the path back in
* adding the full path
* overriding the config directory for the snap version test. It doesn't really make sense...
