Merge pull request #28992 from storybookjs/valentin/fix-wrong-nextjs-framework-reference

Next.js: Fix wrong Next.js framework reference

Author: valentinpalkovic

code/frameworks/experimental-nextjs-vite/src/export-mocks/headers/cookies.ts

@@ -1,10 +1,11 @@
 // We need this import to be a singleton, and because it's used in multiple entrypoints
 // both in ESM and CJS, importing it via the package name instead of having a local import
 // is the only way to achieve it actually being a singleton
+import { fn } from '@storybook/test';
+
 // eslint-disable-next-line @typescript-eslint/ban-ts-comment
 // @ts-ignore we must ignore types here as during compilation they are not generated yet
-import { headers } from '@storybook/nextjs/headers.mock';
-import { fn } from '@storybook/test';
+import { headers } from '@storybook/experimental-nextjs-vite/headers.mock';
 
 import { RequestCookies } from 'next/dist/compiled/@edge-runtime/cookies';
 

code/frameworks/nextjs/src/preview.tsx

@@ -5,7 +5,6 @@ import type { Addon_DecoratorFunction, Addon_LoaderFunction } from 'storybook/in
 // is the only way to achieve it actually being a singleton
 // eslint-disable-next-line @typescript-eslint/ban-ts-comment
 // @ts-ignore we must ignore types here as during compilation they are not generated yet
-import { cookies, headers } from '@storybook/nextjs/headers.mock';
 // eslint-disable-next-line @typescript-eslint/ban-ts-comment
 // @ts-ignore we must ignore types here as during compilation they are not generated yet
 import { createNavigation } from '@storybook/nextjs/navigation.mock';