Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Update .gitignore * Upgrade to Yarn v3 Following https://yarnpkg.com/getting-started/migration * Bump local version of node to v14 to match prod * Initial yarn install after upgrade to yarn v3 * Add yarn workspaces plugin * Lock node version, update CI to use yarn3 * Fix import * Add missing dependency * Refactor: move __tests__ to src for consistency * Refactor: uniquely name different table components * Refactor: uniquely name Tooltip components * Localise dependencies to each workspace. This is a change from Yarn1 to Yarn2: "Only the dependencies depended upon by a workspace can be accessed". see https://yarnpkg.com/features/workspaces/#what-does-it-mean-to-be-a-workspace * Reuse common scripts * Use babel instead of rollup for admin panel lib * Bump gold master to node v14 * Admin panel simpler lib build * Bump e2e Dockerfile to node 14 The latest cypress/base docker image has node 14.19.0 * Add missing dep * Minor: Remove comment * Add missing @types dependency * Add missing dep for e2e testing * Refactor: extract e2e into own package * Simplify e2e Dockerfile * Add missing package * Less verbose yarn output * Add build-dev script to packages This differentiates it from the normal build script, which is used for production releases. Typically we only want to build to a state where a developer can start work, or tests can be run on a package etc. One direct advantage is that admin panel no longer does a production build after each yyarn install. * Remove dependency on curl in e2e * Add .npmrc files See https://stackoverflow.com/a/51295237 * Use npm run instead of yarn for performance * Fix e2e test run * Fix broken build script * Fix test e2e * Fix test scripts * Fix test run scripts * Update CI e2e env vars * Use yarn x for non-build scripts * PR fixups add missing env var
- Loading branch information