Fix(deps):major upgrade Nuxt 4 & Storybook 10 #980
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.
chore: pin Nuxt to 4.1.3 for Storybook 10 ESM-only compatibility
Pin Nuxt to 4.1.3 (4.2.0+ breaks Storybook 10 integration)
Update peerDependencies to ^4.0.0 <4.2.0
Document limitation in README
Fix showcase runtimeConfig warnings
ESM preset build output (preset.mjs)
Package name exports in core (instead of resolved paths)
ESM export in package.json
Pin Nuxt to 4.1.3 in all examples (4.2.0+ breaks Storybook 10)
Update peerDependencies to ^4.0.0 <4.2.0
Document limitation in README
Fix showcase runtimeConfig to use public namespace
-Fix Nuxt 4 warnings about reserved app namespace in runtimeConfig
🔗 Linked issue
📚 Description