* reinstate
* start server manually
* routing tests too
* skip more
* sleep more and fail if not 200
* use e2etest for content/ too
* automatically start server for jest
* does this work?
* feedbacked
* rename things
* getting it to work
* add dev dependency
* install the right version
* don't need to start that
* fix package lock
* update readme about it
* feedbacked
* don't need disk caching for site-data
* sync serialize sitedata to disk
* use os.tmpdir
* refactor tests
* debugging
* use log
* debugging
* louder about syntax errors
* warn-before-tests
* louder about disk-caching redirects
* less loud
* only in development again
* First run of script
* Get the app running --- ish
* Get NextJS working
* Remove `node:`
* Get more tests passing in unit directory
* Update FailBot test to use nock
* Update test.yml
* Update Dockerfile
* tests/content fixes
* Update page.js
* Update build-changelog.js
* updating tests/routing
* Update orphan-tests.js
* updating tests/rendering
* Update .eslintrc.js
* Update .eslintrc.js
* Install jest/globals
* "linting" tests
* staging update to server.mjs
* Change '.github/allowed-actions.js' to a ESM export
* Lint
* Fixes for the main package.json
* Move Jest to be last in the npm test command so we can pass args
* Just use 'npm run lint' in the npm test command
* update algolia label script
* update openapi script
* update require on openapi
* Update enterprise-algolia-label.js
* forgot JSON.parse
* Update lunr-search-index.js
* Always explicitly include process.cwd() for JSON file reads pathed from project root
* update graphql/update-files.js script
* Update other npm scripts using jest to pass ESM NODE_OPTIONS
* Update check-for-enterprise-issues-by-label.js for ESM
* Update create-enterprise-issue.js for ESM
* Import jest global for browser tests
* Convert 'script/deploy' to ESM
Co-authored-by: Grace Park <gracepark@github.com>
Co-authored-by: James M. Greene <jamesmgreene@github.com>
