[Bug]: eslint-plugin-storybook no-renderer-packages references @storybook/experimental-nextjs-vite

[oskari]

Describe the bug

The rule no-renderer-packages still references experimental-nextjs-vite, while it's stable now:
Do not import renderer package "@storybook/react" directly. Use a framework package instead (e.g. @storybook/nextjs, @storybook/react-vite, @storybook/react-webpack5, @storybook/react-native-web-vite, @storybook/experimental-nextjs-vite).eslint[storybook/no-renderer-packages](https://github.com/storybookjs/storybook/blob/next/code/lib/eslint-plugin/docs/rules/no-renderer-packages.md)

Reproduction link

https://stackblitz.com/edit/github-ebvuvuxa?file=src%2Fstories%2FButton.stories.ts

Reproduction steps

1. Go to above repro link
2. run npx eslint .
3. See error about Button.stories.ts file

System

Storybook Environment Info:

  System:
    OS: macOS 15.6
    CPU: (10) arm64 Apple M1 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.21.0 - ~/.nvm/versions/node/v22.21.0/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 10.9.4 - ~/.nvm/versions/node/v22.21.0/bin/npm <----- active
  npmPackages:
    @storybook/addon-a11y: ^10.0.0 => 10.0.0
    @storybook/addon-docs: ^10.0.0 => 10.0.0
    @storybook/addon-onboarding: ^10.0.0 => 10.0.0
    @storybook/addon-themes: ^10.0.0 => 10.0.0
    @storybook/addon-vitest: ^10.0.0 => 10.0.0
    @storybook/nextjs-vite: ^10.0.0 => 10.0.0
    chromatic: ^13.3.2 => 13.3.2
    eslint-plugin-storybook: ^10.0.0 => 10.0.0
    msw-storybook-addon: ^2.0.6 => 2.0.6
    storybook: ^10.0.0 => 10.0.0
    storybook-next-intl: ^2.0.13 => 2.0.13

Additional context

No response

[dosubot]

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

You're right—the no-renderer-packages rule in eslint-plugin-storybook still references @storybook/experimental-nextjs-vite in its suggestions and documentation, even though the stable package is now @storybook/nextjs-vite. This is just a messaging/documentation oversight and doesn't affect functionality. The migration docs confirm that @storybook/experimental-nextjs-vite has been fully replaced by @storybook/nextjs-vite, so your setup is correct and you can safely ignore the outdated suggestion for now. This should be updated in a future release to avoid confusion.

References:

• Rule implementation and docs still mention the experimental package
• Migration notes on the stable package

To reply, just mention @dosu.

---

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