Dependencies: Update vite-plugin-storybook-nextjs
to 2.0.7
#32331
+6
−6
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.
storybookjs/vite-plugin-storybook-nextjs#50
What I did
Upgrading the version of
vite-plugin-storybook-nextjs
that@storybook/nextjs-vite
depends on.This is intended to resolve the
[Error: Dynamic require of "next/dist/build/webpack/plugins/define-env-plugin.js" is not supported"]
error that is occurring in the current version.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 PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the
@storybookjs/core
team here.core team members can create a canary release here or locally with
gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>
Greptile Summary
This PR updates the
vite-plugin-storybook-nextjs
dependency in the@storybook/nextjs-vite
package from version^2.0.5
to^2.0.7
. This is a targeted bug fix update that addresses a specific runtime error:Dynamic require of "next/dist/build/webpack/plugins/define-env-plugin.js" is not supported
.The
@storybook/nextjs-vite
framework is designed to integrate Storybook with Next.js applications using Vite as the build tool. It depends onvite-plugin-storybook-nextjs
as its core plugin to handle Next.js-specific features and compatibility within the Vite environment. This plugin is essential for features like Next.js routing, image optimization, and other framework-specific functionality to work properly in Storybook.The error being fixed appears to be related to ESM/CommonJS compatibility issues when the plugin tries to dynamically require Next.js internal modules. Version 2.0.7 of the plugin contains fixes for this compatibility issue, ensuring that Next.js features work correctly in Vite-based Storybook setups. The change maintains the caret range (
^2.0.7
) which follows semantic versioning practices and allows for future patch updates while ensuring the minimum version includes the necessary fixes.PR Description Notes:
Confidence score: 4/5
code/frameworks/nextjs-vite/package.json
file should be reviewed to ensure the version update is correct