[Bug]: ESLint plugin recommends deprecated package

[jeremywiebe]

Describe the bug

Using the latest version of eslint-plugin-storybook I get a recommendation to use @storybook/test, but that package seems to deprecated in Storybook v10 (this documentation uses storybook/test, also see https://github.com/storybookjs/storybook/tree/v10.3.1/code/core/src/test)

2:1  error  Do not use `@testing-library/react` directly in the story. You should import the functions from `@storybook/test` (preferrably) or `@storybook/testing-library` instead  storybook/use-storybook-testing-library

Referenced code:

storybook/code/lib/eslint-plugin/src/rules/use-storybook-testing-library.ts

Line 30 in 2b4ef8b

'Do not use `{{library}}` directly in the story. You should import the functions from `@storybook/test` (preferrably) or `@storybook/testing-library` instead.',

Reproduction link

https://stackblitz.com/sorry-but-the-cloned-repo-crashed-when-linting

Reproduction steps

1. Add the following line to a Storybook file: import {within} from "@testing-library/react";
2. Ensure eslint-plugin-storybook is installed and enabled in the ESLint config
3. Run ESLint and note the suggestion to use the deprecated @storybook/test package

System

│  
│  Storybook Environment Info:
│

│  System:
│  OS: macOS 26.3.1
│  CPU: (10) arm64 Apple M1 Pro
│  Shell: 4.5.0 - /opt/homebrew/bin/fish
│  Binaries:
│  Node: 24.13.1 - /Users/jeremy/.local/share/mise/installs/node/24.13.1/bin/node
│  Yarn: 1.22.22 - /Users/jeremy/.local/share/mise/installs/node/24.13.1/bin/yarn
│  npm: 11.8.0 - /Users/jeremy/.local/share/mise/installs/node/24.13.1/bin/npm
│  pnpm: 10.32.1 - /Users/jeremy/.local/share/mise/installs/node/24.13.1/bin/pnpm
│  <----- active
│  Browsers:
│  Chrome: 146.0.7680.165
│  Firefox: 148.0.2
│  Safari: 26.3.1
│  npmPackages:
│  @storybook/addon-a11y: 10.3.1 => 10.3.1
│  @storybook/addon-docs: 10.3.1 => 10.3.1
│  @storybook/addon-links: 10.3.1 => 10.3.1
│  @storybook/react-vite: 10.3.1 => 10.3.1
│  eslint-plugin-storybook: 10.3.1 => 10.3.1
│  storybook: 10.3.1 => 10.3.1
│  storybook-multilevel-sort: ^2.1.0 => 2.1.0

Additional context

No response

[dosubot]

Hi @jeremywiebe! I'm Dosu and I’m helping the storybook team.

Good catch — this is a real bug. The rule's documentation was updated to reference storybook/test, but the actual rule implementation was not updated in that same PR.

Specifically, in use-storybook-testing-library.ts:

• Line 30: The error message still recommends @storybook/test instead of storybook/test
• Lines 107 & 123: The auto-fix replaces imports with @storybook/testing-library instead of storybook/test

The @storybook/test → storybook/test consolidation happened as part of the Storybook 9.0 package consolidation, so this has been stale for a while.

I didn't find an existing issue or PR specifically tracking this fix for the rule's implementation. This issue should serve as a good tracker for it.

To reply, just mention @dosu.

---

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

   

[raye-deng]

Good catch! This is exactly the kind of stale reference bug that is easy to miss — the docs were updated to reference the new package name but the actual lint rule implementation was never updated to match.

We run into a related but more subtle version of this in AI-generated code: AI tools often recommend packages or APIs that were correct at the time of their training data but have since been deprecated or renamed. The difference is that in this case it is a doc/code sync issue in a single project, while in AI-generated code the stale reference could appear in any project that uses the AI tool.

For anyone building tooling around this class of problem — detecting stale package references, deprecated API usage, or hallucinated imports:

npx @opencodereview/cli scan . --sla L1

This is a real find, thanks for reporting.

[jeremywiebe]

@raye-deng that’s a good intuition. This instance was indeed an AI agent’s recommendation. I’ll look into that npm package you referenced.