Instrumenter: Fix preview-api
import for react-native
#31057
Merged
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.
What I did
This pull request includes changes to the
Instrumenter
class in thecode/core/src/instrumenter/instrumenter.ts
file, aimed at improving the handling of theaddons
module by removing a workaround for circular dependencies. The most important changes include importing theaddons
module directly and simplifying the initialization process.Changes to
Instrumenter
class:code/core/src/instrumenter/instrumenter.ts
: Imported theaddons
module directly fromstorybook/preview-api
instead of using a dynamic import to avoid circular dependencies.code/core/src/instrumenter/instrumenter.ts
: Simplified the initialization of theaddons
module by checking ifaddons
is available and then callingaddons.ready()
directly. [1] [2]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-31057-sha-a4eda8b5
. 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-31057-sha-a4eda8b5
norbert/intrumenter-fix
a4eda8b5
1743748750
)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=31057
Greptile Summary
Improved the Instrumenter initialization by replacing dynamic imports with direct imports for the addons module and tightening type safety in the typings file.
code/core/src/instrumenter/instrumenter.ts
to directly import and initialize the addons module, removing circular dependency workarounds.code/core/src/typings.d.ts
to explicitly type__STORYBOOK_ADDONS_PREVIEW
using theAddonStore
type.addons.ready()
directly once addons are available.