fix: update Nuxt 4 peer dependency and @nuxt/kit constraints#206
Open
anzzyspeaksgit wants to merge 1 commit intoDevelopmint:mainfrom
Open
fix: update Nuxt 4 peer dependency and @nuxt/kit constraints#206anzzyspeaksgit wants to merge 1 commit intoDevelopmint:mainfrom
anzzyspeaksgit wants to merge 1 commit intoDevelopmint:mainfrom
Conversation
Closes Developmint#203 Updates package dependencies to officially support Nuxt 4 alongside Nuxt 3. - Loosens `@nuxt/kit` to `^3.2.0 || ^4.0.0` - Explicitly adds `nuxt: ^3.0.0 || ^4.0.0` to `peerDependencies` This ensures package managers properly resolve Nuxt 4 versions without complaining about incompatibilities.
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
1 participant
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.
Summary
Updates the package.json to fully support Nuxt 4 alongside Nuxt 3 by loosening the
@nuxt/kitdependency constraint.Problem
Closes #203
Even after #199 updated the module compatibility property, package managers (and Nuxt 4 itself) could still log warnings or duplication errors because
@nuxt/kitwas strictly pinned to^3.2.0, and Nuxt wasn't defined inpeerDependencies.Solution
@nuxt/kitto allow both^3.2.0 || ^4.0.0.nuxt: ^3.0.0 || ^4.0.0topeerDependenciesas recommended in the Nuxt 4 Module Upgrade Guide.Testing
This PR was created with AI assistance.