CSF: Fix Canvas and userEvent types under Yarn PnP#34986
Merged
valentinpalkovic merged 3 commits intoJun 3, 2026
Conversation
…oundFunctions from testing-library. This improves integration with user interactions in tests.
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughThis PR consolidates testing-library type definitions by moving ChangesTesting-Library Type Integration
🎯 2 (Simple) | ⏱️ ~12 minutes Comment |
valentinpalkovic
approved these changes
Jun 3, 2026
20 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #30763
What I did
Fixes
CanvasandStoryContext.userEventtypes not resolving inplayfunctions under Yarn PnP (and other strict TS setups).Root cause.
code/core/src/test/index.tswas contributing those types via adeclare module 'storybook/internal/csf'augmentation. Module augmentations only take effect when TypeScript actually loads the augmenting module into its program. Under Yarn PnP, that load doesn't happen automatically, so consumers got the emptyinterface Canvas {}shipped indist/csf/index.d.tsand aStoryContextwith nouserEventfield — manifesting asProperty 'findByRole' does not exist on type 'Canvas'and similar errors.The workarounds that circulated on the issue (
import 'storybook/test'in every story,"types": ["storybook/test"]intsconfig.json, adding@storybook/coreto user deps,.yarnrc.yml packageExtensions) all worked but pushed the burden onto every user.Fix. Declare the real types directly on the base interfaces in
code/core/src/csf/story.tsinstead of augmenting them from outside:interface Canvas extends BoundFunctions<typeof queries> {}StoryContextgainsuserEvent: ReturnType<typeof userEvent.setup>…and remove the now-redundant
declare moduleblock (plus its supporting imports/aliases) fromcode/core/src/test/index.ts.Why this is safe.
import typeonly — zero runtime impact.@testing-library/domand@testing-library/user-eventare already direct runtime dependencies ofstorybook(seecode/core/package.json), so no new dependency is added.CanvasandStoryContext.userEventexactly as documented; they just now resolve correctly regardless of package manager or tsconfig.Checklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
This is a type-only change to interface declarations in
code/core/src/csf/story.ts. There is no runtime behavior to test, and the existingyarn nx check core(run as part of CI) exercises the new declarations against the rest of the type graph in the monorepo — that target passes locally.Manual testing
Caution
This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!
Reproduction steps for the original bug (current
next, before this fix):tsconfig.jsonwith"moduleResolution": "Bundler"and a story-like file usingcanvasinside aplayfunction:yarn tsc --noEmit.Before this PR:
After this PR (using a tarball packed from this branch via
yarn nx compile core -c production && yarn workspace storybook pack):Documentation
MIGRATION.MD
No docs update required — the public types remain
CanvasandStoryContext.userEventexactly as documented. This PR makes them resolve in the cases where they previously didn't.Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal,ci:mergedorci:dailyGH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli-storybook/src/sandbox-templates.tsMake sure this PR contains one of the labels below:
Available labels
bug: Internal changes that fixes incorrect behavior.maintenance: User-facing maintenance tasks.dependencies: Upgrading (sometimes downgrading) dependencies.build: Internal-facing build tooling & test updates. Will not show up in release changelog.cleanup: Minor cleanup style change. Will not show up in release changelog.documentation: Documentation only changes. Will not show up in release changelog.feature request: Introducing a new feature.BREAKING CHANGE: Changes that break compatibility in some way with current major version.other: Changes that don't fit in the above categories.Suggested label:
bug.🦋 Canary release
This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the
@storybookjs/coreteam here.core team members can create a canary release here or locally with
gh workflow run --repo storybookjs/storybook publish.yml --field pr=<PR_NUMBER>Summary by CodeRabbit
Release Notes