-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
React: Use Act wrapper in Storybook for component rendering #30037
Conversation
View your CI Pipeline Execution ↗ for commit b0737e7.
☁️ Nx Cloud last updated this comment at |
b4a1714
to
4c40b5f
Compare
4c40b5f
to
95e2429
Compare
95e2429
to
13e3869
Compare
Package BenchmarksCommit: The following packages have significant changes to their size or dependencies:
|
Before | After | Difference | |
---|---|---|---|
Dependency count | 153 | 153 | 0 |
Self size | 231 KB | 231 KB | 🚨 +298 B 🚨 |
Dependency size | 44.67 MB | 44.69 MB | 🚨 +16 KB 🚨 |
Bundle Size Analyzer | Link | Link |
@storybook/nextjs
Before | After | Difference | |
---|---|---|---|
Dependency count | 589 | 589 | 0 |
Self size | 471 KB | 472 KB | 🚨 +298 B 🚨 |
Dependency size | 83.25 MB | 83.27 MB | 🚨 +16 KB 🚨 |
Bundle Size Analyzer | Link | Link |
…ENV handling in build scripts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
5 file(s) reviewed, 5 comment(s)
Edit PR Review Bot Settings | Greptile
76e10e5
to
32b52ee
Compare
32b52ee
to
a52aec2
Compare
- Introduced a new feature flag `developmentModeForBuild` to enhance testability in built Storybooks. - Updated build configurations to set `process.env.NODE_ENV` to `development` when the feature is enabled. - Cleaned up unnecessary definitions in various preset and configuration files.
e67cc92
to
45971d9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for documenting this! Made some edits as suggestions.
Co-authored-by: Kyle Gach <[email protected]>
Co-authored-by: Kyle Gach <[email protected]>
Closes #
What I did
Previously, we have wrapped mounting and unmounting of React component, as well as test interactions via userEvent by
act
in a portable stories environment. Now we are adapting this behaviour to configure@storybook/test
to wrap all component interactions and mounting/unmounting withact
. This will make sure, that we can actually await a components rendering properly before we continue to the next Storybook render lifecycle phase.Background:
The A11y addon has issues to find the right timing to trigger an automated test run if a component uses Suspense (e.g. RSC). With
act
we can actually properly await the complete rendering of a React component also in the Storybook preview, so that addon a11y can properly await its final rendering to trigger an a11y test run.Introducing
features.developmentModeForBuild
As part of our ongoing efforts to improve the testability and debuggability of Storybook, we are introducing a new feature flag:
developmentModeForBuild
. This feature flag allows you to setprocess.env.NODE_ENV
todevelopment
in built Storybooks, enabling development-related optimizations that are typically disabled in production builds.In development mode, React and other libraries often include additional checks and warnings that help catch potential issues early. These checks are usually stripped out in production builds to optimize performance. However, when running tests or debugging issues in a built Storybook, having these additional checks can be incredibly valuable. One such feature is React's
act
, which ensures that all updates related to a test are processed and applied before making assertions.act
is crucial for reliable and predictable test results, but it only works correctly whenNODE_ENV
is set todevelopment
.Checklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!
Documentation
MIGRATION.MD
Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal
,ci:merged
orci:daily
GH 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.ts
Make 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.🦋 Canary release
This pull request has been released as version
0.0.0-pr-30037-sha-45971d9d
. Try it out in a new sandbox by runningnpx [email protected] sandbox
or in an existing project withnpx [email protected] upgrade
.More information
0.0.0-pr-30037-sha-45971d9d
valentin/act-wrapping-of-components
45971d9d
1734607856
)To request a new release of this pull request, mention the
@storybookjs/core
team.core team members can create a new canary release here or locally with
gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=30037
Greptile Summary
Based on the provided files and changes, here's a concise summary of the pull request:
Implements proper React act() wrapping for component rendering in Storybook, ensuring consistent behavior between development and testing environments.
act-compat.ts
to skip act wrapping in production buildsrenderToCanvas.tsx
to wrap both render and unmount operations in act() for proper component lifecycle handling__isPortableStory
flag in render context to control act wrapping behavior