You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During testing my middleware (Edge runtime) I faced with the issue - runtime isn't changing.
Code and configuration below, can assume that's misconfiguration.
The simple test below has passed, although it shouldn't
constnextJest=require('next/jest');constcreateJestConfig=nextJest({// Provide the path to your Next.js app to load next.config.js and .env files in your test environmentdir: './',});// Add any custom config to be passed to JestconstcustomJestConfig={setupFilesAfterEnv: ['<rootDir>/jest.setup.js'],testEnvironment: 'jsdom',};// createJestConfig is exported this way to ensure that next/jest can load the Next.js config which is asyncmodule.exports=createJestConfig(customJestConfig);
Bug Report
Current behavior
During testing my middleware (Edge runtime) I faced with the issue - runtime isn't changing.
Code and configuration below, can assume that's misconfiguration.
The simple test below has passed, although it shouldn't
Expected behavior/code
Switching environment to runtime edge
Additional context/screenshots
test.js
jest.config.js
jest.setup.js
devDeps from
package.json
:The text was updated successfully, but these errors were encountered: