Fix jest config setupFilesAfterEnv (conflict between package.json:jest and jest.config.js) - See jestjs/jest#10123

Author: Vadorequest

jest.config.js

@@ -11,6 +11,10 @@ module.exports = {
     },
   },
   modulePathIgnorePatterns: [
-    'cypress'
-  ]
+    'cypress',
+  ],
+  setupFilesAfterEnv: [
+    'jest-extended',
+    './jest.setup.js',
+  ],
 };

jest.setup.js

@@ -1,4 +1,4 @@
-import fetch from 'node-fetch';
+const fetch = require('node-fetch');
 
 /**
  * @see https://github.com/vercel/next.js/discussions/13678 How to use built-in fetch in tests?
@@ -8,4 +8,4 @@ import fetch from 'node-fetch';
 // Polyfill "fetch" for node.js, so that our tests may replicate the built-in "fetch" provided by Next.js
 global.fetch = fetch;
 
-console.info('Jest env has been enhanced - See "./jest.setup.js"')
+console.info('Jest env has been enhanced - See "./jest.setup.js"');

package.json

@@ -44,12 +44,6 @@
     "security:audit": "yarn audit",
     "packages:upgrade": "yarn upgrade-interactive --latest"
   },
-  "jest": {
-    "setupFilesAfterEnv": [
-      "jest-extended",
-      "./jest.setup.js"
-    ]
-  },
   "dependencies": {
     "@amplitude/react-amplitude": "1.0.0",
     "@emotion/core": "10.0.28",