chore: fix integration test run

Author: vonovak

jest.config.integration.js

@@ -7,7 +7,8 @@ module.exports = {
   ...sourceConfig,
   projects: sourceConfig.projects.map((project) => ({
     ...project,
-    // Redirect imports to the compiled bundles
+    // Redirect imports to the compiled bundles.
+    // This is to test compiled code instead of source (applies to code under test and also its deps).
     moduleNameMapper: {},
   })),
 

package.json

@@ -11,7 +11,7 @@
     "test": "jest",
     "test:ci": "jest --ci --runInBand",
     "test:ci:coverage": "yarn test:ci --coverage",
-    "test:integration": "jest -c jest.config.integration.js",
+    "test:integration": "yarn node --experimental-vm-modules $(yarn bin jest) -c jest.config.integration.js",
     "test:e2e": "yarn workspaces foreach -p run test:e2e",
     "test:tsd": "jest -c jest.config.types.js",
     "test:all": "yarn test && yarn test:integration && yarn test:e2e && test:tsd",
@@ -51,7 +51,7 @@
     "@typescript-eslint/eslint-plugin": "^5.50.0",
     "@typescript-eslint/parser": "^5.50.0",
     "babel-eslint": "^10.1.0",
-    "babel-jest": "^29.4.3",
+    "babel-jest": "^29.7.0",
     "chalk": "^4.1.0",
     "cross-env": "^7.0.2",
     "eslint": "^7.32.0",
@@ -61,9 +61,9 @@
     "eslint-plugin-node": "^11.1.0",
     "eslint-plugin-promise": "^4.1.1",
     "husky": "^8.0.3",
-    "jest": "^29.4.3",
-    "jest-environment-jsdom": "^29.4.3",
-    "jest-environment-node-single-context": "^29.0.0",
+    "jest": "^29.7.0",
+    "jest-environment-jsdom": "^29.7.0",
+    "jest-environment-node-single-context": "^29.4.0",
     "jest-runner-tsd": "^4.0.0",
     "lerna": "^6.5.1",
     "lint-staged": "^13.1.0",
@@ -78,7 +78,7 @@
     "size-limit": "^8.1.1",
     "strip-ansi": "^6.0.1",
     "swc-node": "^1.0.0",
-    "ts-jest": "^29.0.5",
+    "ts-jest": "^29.2.4",
     "typescript": "^4.9.5"
   },
   "workspaces": [

packages/loader/src/webpackLoader.ts

@@ -54,11 +54,10 @@ Please check that \`catalogs.path\` is filled properly.\n`
     sourceLocale: config.sourceLocale,
   })
 
-  // In production we don't want untranslated strings. It's better to use message
+  // In production, we don't want untranslated strings. It's better to use message
   // keys as a last resort.
   // In development, however, we want to catch missing strings with `missing` parameter
-  // of I18nProvider (React) or setupI18n (core) and therefore we need to get
-  // empty translations if missing.
+  // of setupI18n (core) and therefore we need to get empty translations if missing.
   const strict = process.env.NODE_ENV !== "production"
 
   return createCompiledCatalog(locale, messages, {