refactor: migrate from Jest to Vitest
It does so by:
- Installing vitest dependencies and removing the jest dependencies.
- Changing the test target in the Makefile to use Vitest.
- Changing the CI pipelines to use Vitest instead of Jest.
- Removing jest configuration from eslint.config.js and adding the
vitest eslint plugin.
This commit also fixes some issues in the FetchProxy test suite.
Fixed: twpowertools:236
Change-Id: I6a6a636cd5e943194ff6b06c17a150537659d586
diff --git a/Makefile b/Makefile
index a2c4b31..e3d8de8 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
.PHONY: node_deps clean_dist deps clean_deps lit_localize_extract lit_localize_build lit_localize_all serve_chromium_mv3 serve_gecko release release_chromium_stable release_chromium_beta release_chromium_canary release_gecko_stable build_test_extension clean_releases test clean trigger_nightly_build
WEBPACK := ./node_modules/webpack-cli/bin/cli.js
-JEST := node ./node_modules/jest/bin/jest.js
+VITEST := pnpm exec vitest
RELEASE_SCRIPT := bash tools/release.bash
grpc_proto_gen:
@@ -68,7 +68,7 @@
rm -rf out
test:
- $(JEST)
+ $(VITEST)
clean: clean_deps clean_dist clean_releases