* Create devcontainer for codespaces
* Use node 16 for devcontainer and CI
* Fix node version incompatibility error
* Remove caching
* Add npm build to check-dist
* Remove new caching
* use npm install
* Test node 14
* Update check dist with node 16
* Use node 18.x for check-dist
* Npm install vs CI
* Update package.json scripts
* test
* Remove caching
* npm run test
* testing
* test
* test
* One more test
* Test
* test
* Update everything
* use vercel
* Test
* Update index.js
* Test
* Remove codeql warnings
* Use NPM CI vs install
* Small tweaks to existing workflows
* Create check-dist.yml
* steps.if still needs ${{ }} when the expr has operators
* single quotes?
* npm install
* mess with index.js
* add if failure()
* Copy the correct version back in from the artifact
* Update .github/workflows/check-dist.yml
Co-authored-by: Konrad Pabjan <konradpabjan@github.com>
* formatting & language
* npm ci
Co-authored-by: Konrad Pabjan <konradpabjan@github.com>
From February 2021, in order to provide feedback on pull requests, Code Scanning workflows must be configured with both `push` and `pull_request` triggers. This is because Code Scanning compares the results from a pull request against the results for the base branch to tell you only what has changed between the two.
Early in the beta period we supported displaying results on pull requests for workflows with only `push` triggers, but have discontinued support as this proved to be less robust.
See https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#scanning-pull-requests for more information on how best to configure your Code Scanning workflows.
Luís Ferreira