npm upgrade
Home@storybook/react 9 → 10
9.1.20 → 10.6.0. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
@storybook/react 10.6.0 removes or renames exports your code may import.
- Removed
- 31
- Renamed
- 0
- Signature changes
- 0
- Types removed
- 0
- Newly deprecated
- 0
- Added
- 0
Does this break your code?
Run this in your project. It compares both releases against the names your code actually imports, locally, with no account and nothing sent to lurq:
npx lurqrun check-upgrade --upgrade @storybook/react@9.1.20..10.6.0
To have your coding agent check upgrades like this before it writes them, connect lurq to Claude Code, Cursor, VS Code or Codex:
npx lurqrun
Removed
Gone at runtime, with no replacement found under another name. Imports of these fail.
- Nodeobject
- Parserobject
- Positionobject
- SourceLocationobject
- TokContextobject
- Tokenobject
- TokenTypeobject
- applyDecoratorsfunction
- argTypesEnhancersobject
- beforeAllfunction
- decoratorsobject
- defaultobject
- defaultOptionsobject
- getLineInfofunction
- isIdentifierCharfunction
- isIdentifierStartfunction
- isNewLinefunction
- keywordTypesobject
- lineBreakobject
- lineBreakGobject
- mountfunction
- nonASCIIwhitespaceobject
- parametersobject
- parsefunction
- parseExpressionAtfunction
- renderfunction
- renderToCanvasfunction
- tokContextsobject
- tokTypesobject
- tokenizerfunction
- versionobject
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Sep 10, 2026. @storybook/react on lurq.