Add vercel/pkg to create standalone CLI

.github/workflows/cli.yml

@@ -9,10 +9,18 @@ jobs:
     steps:
     - uses: actions/checkout@v2
 
-    # Build the CLI
     - name: Build CLI
-      run: npm run build-cli
+      run: |
+        cd packaging
+        npm install
+        npm run build-cli
 
-    # Upload an empty SARIF file
     - name: Upload with CLI
-      run: node cli/code-scanning-cli.js upload --sarif-file src/testdata/empty-sarif.sarif --repository $GITHUB_REPOSITORY --commit $GITHUB_SHA --ref $GITHUB_REF --github-url $GITHUB_API_URL --github-auth ${{ github.token }}
+      run: |
+        packaging/dist/code-scanning-cli-linux upload \
+          --sarif-file src/testdata/empty-sarif.sarif \
+          --repository $GITHUB_REPOSITORY \
+          --commit $GITHUB_SHA \
+          --ref $GITHUB_REF \
+          --github-url $GITHUB_API_URL \
+          --github-auth ${{ github.token }}

.gitignore

@@ -1,2 +1,2 @@
-/cli/
-
+/packaging/dist/
+/packaging/node_modules/

CONTRIBUTING.md

@@ -49,6 +49,10 @@ Running locally will generate the CodeQL database and run all the queries, but i
 
 As well as the unit tests (see _Common tasks_ above), there are integration tests, defined in `.github/workflows/integration-testing.yml`.  These are run by a CI check.  Depending on the change you’re making, you may want to add a test to this file or extend an existing one.
 
+### Building the CLI
+
+Navigate to the `packaging` directory and run `npm install` to install dependencies needed only for compiling the CLI. Run `npm run build-cli` to output files to the `packaging/dist` directory.
+
 ## Submitting a pull request
 
 1. [Fork][fork] and clone the repository