Storybook works locally but not when deployed

[valentinpalkovic]

Discussed in #33781

^{Originally posted by lsarni February 5, 2026}

Summary

I'm migrating to Storybook v10 on Next.js v16, and it works locally, but on production all stories give the following error:

memo is not defined
The component failed to render properly, likely due to a configuration issue in Storybook. Here are some common causes and how you can address them:

Missing Context/Providers: You can use decorators to supply specific contexts or providers, which are sometimes necessary for components to render correctly. For detailed instructions on using decorators, please visit the [Decorators documentation](https://storybook.js.org/docs/writing-stories/decorators).
Misconfigured Webpack or Vite: Verify that Storybook picks up all necessary settings for loaders, plugins, and other relevant parameters. You can find step-by-step guides for configuring [Webpack](https://storybook.js.org/docs/builders/webpack) or [Vite](https://storybook.js.org/docs/builders/vite) with Storybook.
Missing Environment Variables: Your Storybook may require specific environment variables to function as intended. You can set up custom environment variables as outlined in the [Environment Variables documentation](https://storybook.js.org/docs/configure/environment-variables).

I can't find any previous references of this.

Additional information

No response

Create a reproduction

No response

[dosubot]

Another user (@kcrwfrd) ran into the same memo is not defined error when upgrading to Next.js 16 + Storybook 10 with @storybook/nextjs (webpack). The root cause is webpack's innerGraph optimization — it's production-only, which is why dev works fine. It incorrectly strips the memo binding from storybook/dist/components/index.js while leaving code that still references it [1].

Two workarounds:

1. Disable innerGraph in .storybook/main.ts:

   webpackFinal: async (storybookConfig) => {
     storybookConfig.optimization = storybookConfig.optimization || {}
     storybookConfig.optimization.innerGraph = false
     return storybookConfig
   }

2. Switch to @storybook/nextjs-vite, which sidesteps the webpack issue entirely [1].

Could you share your exact Storybook and Next.js versions, and confirm whether you're using webpack or Vite? That'll help confirm this is the same issue.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.