Skip to content

Docs: Adjust mocking modules #32808

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jonniebigodes merged 2 commits into from
Oct 23, 2025
Merged

Docs: Adjust mocking modules #32808

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
37234bc
Docs: Adjust mocking modules
jonniebigodes Oct 23, 2025
f472ebf
Merge branch 'next' into docs_fix_mocking_modules
jonniebigodes Oct 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/writing-stories/mocking-data-and-modules/mocking-modules.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -331,3 +331,7 @@ Here's an example of using the [`mockdate`](https://github.com/boblauer/MockDate
### Receiving an `exports is not defined` error

Webpack projects may encounter an `exports is not defined` error when using [automocking](#automocking). This is usually caused by attempting to mock a module with CommonJS (CJS) entry points. Automocking with Webpack only works with modules that have ESModules (ESM) entry points exclusively, so you must use a [mock file](#mock-files) to mock CJS modules.

### Mocking conflicts with other testing tools

If you've already set up mocking with other testing tools (e.g., [Jest](https://jestjs.io/)), you may encounter conflicts when using Storybook's mocking system. These conflicts can cause unexpected behavior, errors, or incorrect mocks when both tools try to mock the same module. This is a known issue when sharing mock files or configurations between Storybook and other testing tools. To address this situation, we recommend that you verify which tool is responsible for mocking a particular module and make sure the configurations do not overlap to avoid any conflicts.