[Bug]: storybookTest seems to not be exported correctly for pnpm

[mmahalwy]

Describe the bug

vitest.workspace.ts:6:10 - error TS2614: Module '"@storybook/addon-vitest/"' has no exported member 'storybookTest'. Did you mean to use 'import storybookTest from "@storybook/addon-vitest/"' instead?

6 import { storybookTest } from '@storybook/addon-vitest/vitest-plugin';
~~~~~~~~~~~~~

Reproduction link

dont have one

Reproduction steps

No response

System

Storybook Environment Info:

  System:
    OS: macOS 15.0.1
    CPU: (8) arm64 Apple M1 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.14.0 - ~/.nvm/versions/node/v22.14.0/bin/node
    npm: 10.9.2 - ~/.nvm/versions/node/v22.14.0/bin/npm
    pnpm: 10.9.0 - ~/.nvm/versions/node/v22.14.0/bin/pnpm <----- active
  Browsers:
    Chrome: 138.0.7204.169
    Edge: 138.0.3351.95
    Safari: 18.0.1
  npmPackages:
    @storybook/addon-docs: ^9.0.18 => 9.0.18 
    @storybook/addon-onboarding: ^9.0.18 => 9.0.18 
    @storybook/addon-styling-webpack: ^2.0.0 => 2.0.0 
    @storybook/addon-vitest: 9.0.18 => 9.0.18 
    @storybook/nextjs-vite: ^9.0.18 => 9.0.18 
    @storybook/react: ^9.0.18 => 9.0.18 
    chromatic: ^11.28.2 => 11.28.2 
    eslint-plugin-storybook: ^9.0.18 => 9.0.18 
    storybook: ^9.0.18 => 9.0.18

Additional context

No response

[dosubot]

The source code for @storybook/addon-vitest/vitest-plugin does export storybookTest as a named export, and the docs show it being used this way. However, pnpm's strict ESM/CJS boundaries can sometimes cause named exports to not be recognized if the built package doesn't emit them correctly, even if the source code does. This is a known interop pitfall and can result in TypeScript errors like the one you're seeing, especially with pnpm or strict ESM settings [source].

If the named import fails, try importing the default export instead:

import storybookTest from '@storybook/addon-vitest/vitest-plugin';
// or, if you need both:
import storybookTestDefault, { storybookTest } from '@storybook/addon-vitest/vitest-plugin';

If that works, it confirms the issue is with how the package is built and how pnpm resolves exports. This is a common pattern with ESM/CJS interop issues, especially after recent ESM migrations in Storybook [source].

There are no official docs or migration notes that address this specific export issue with pnpm, but this workaround is safe and aligns with how other users have resolved similar problems in Storybook packages [source].

If you continue to have trouble, you may want to check your node_modules/.pnpm tree for duplicate or mismatched versions, or try clearing your pnpm store and reinstalling.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[mmahalwy]

this doesnt work

[chkosoptim]

Same problem with yarn:

[yannbf]

Hey everyone, thanks for reporting. Without a reproduction it's hard for us to assist.

Here's a small reproduction environment, you can see that the import works in the vite.config.ts file.
https://stackblitz.com/edit/github-7rwdiphx?file=package.json,vite.config.ts&preset=node

Can you tell us the difference between your project and that, which could be causing the issue? Thanks.

[chkosoptim]

Hey :)

The first major difference I was able to spot is that we are using the latest yarn 4 version (together with the option nodeLinker: node-modules in our .yarnrc.yml) instead of yarn 1 (classic).

[yannbf]

Hey :)

The first major difference I was able to spot is that we are using the latest yarn 4 version (together with the option nodeLinker: node-modules in our .yarnrc.yml) instead of yarn 1 (classic).

Thanks for responding! Unfortunately stackblitz doesn't support yarn berry, however I tested this in other projects using yarn 4 and the issue isn't there. Are you able to make a small reproduction to share?

[pipboy3000]

same problem with npm.

I get the same message as in #32127 (comment)

Storybook Environment Info:

  System:
    OS: macOS 15.5
    CPU: (12) arm64 Apple M4 Pro
    Shell: 5.2.37 - /opt/homebrew/bin/bash
  Binaries:
    Node: 20.10.0 - ~/.local/share/mise/installs/node/20.10.0/bin/node
    Yarn: 1.22.22 - /opt/homebrew/bin/yarn
    npm: 10.2.3 - ~/.local/share/mise/installs/node/20.10.0/bin/npm <----- active
  Browsers:
    Chrome: 138.0.7204.169
    Safari: 18.5
  npmPackages:
    @storybook/addon-vitest: ^9.0.18 => 9.0.18
    @storybook/nextjs: ^9.0.11 => 9.0.11
    @storybook/react: ^9.0.11 => 9.0.11
    storybook: ^9.0.11 => 9.0.18

[mmahalwy]

yeah it doesnt work for pnpm at all :(

[pipboy3000]

Fixed by changing moduleResolution from "node" to "bundler" in tsconfig.json.
Turns out it was just an environment difference with StackBlitz.

[sergei-maertens]

Doesn't seem to work for me with Typescript 5.7 and moduleResolution: "bundler"