imagine if upgrading jest fixes it

jest.config.js

@@ -7,15 +7,9 @@ module.exports = {
   testTimeout: 300000, // 5 minutes in milliseconds
   testRegex: "(/__tests__/.*|(\\.|/)(test|spec))\\.tsx?$",
   verbose: true,
-  globals: {
-    "ts-jest": {
-      diagnostics: false,
-    },
-  },
-  testURL: "http://localhost/",
   testEnvironment: "jsdom",
   transform: {
-    "\\.(ts|tsx|js|jsx)$": "ts-jest",
+    "\\.(ts|tsx|js|jsx)$": ["ts-jest", { diagnostics: false }],
   },
   moduleNameMapper: {
     "\\.(jpg|jpeg|png|gif|eot|otf|webp|svg|ttf|woff|woff2|mp4|webm|wav|mp3|m4a|aac|oga)$":

package.json

@@ -122,7 +122,8 @@
     "html-webpack-plugin": "^5.5.0",
     "husky": "^4.3.0",
     "identity-obj-proxy": "^3.0.0",
-    "jest": "^27.5.1",
+    "jest": "^29.7.0",
+    "jest-environment-jsdom": "^29.7.0",
     "lint-staged": "^12.3.7",
     "mini-css-extract-plugin": "^2.6.0",
     "node-polyfill-webpack-plugin": "^1.1.4",
@@ -137,7 +138,7 @@
     "sass-loader": "^12.6.0",
     "style-loader": "^3.3.1",
     "terser-webpack-plugin": "^5.3.0",
-    "ts-jest": "^27.1.4",
+    "ts-jest": "^29.1.1",
     "ts-loader": "^9.2.8",
     "ts-node": "^10.7.0",
     "tsconfig-paths": "^3.12.0",