Skip to content

Conversation

@danielroe
Copy link
Member

@danielroe danielroe commented Nov 4, 2025

πŸ”— Linked issue

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

this uses the new module dependencies feature in https://github.com/nuxt/nuxt/releases/tag/v4.1.0 to specify options for other modules (and require them).

remake of #4927, pending a fix in nuxt/content

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@github-actions github-actions bot added the v4 #4488 label Nov 4, 2025
@danielroe danielroe changed the title Refactor/deps feat(module)!: use moduleDependencies to manipulate options Nov 4, 2025
@pkg-pr-new
Copy link

pkg-pr-new bot commented Nov 4, 2025

npm i https://pkg.pr.new/@nuxt/ui@5384

commit: cc8fc95

@benjamincanac
Copy link
Member

@danielroe I'm a bit hesitant to merge this as it will break apps that haven't been updated to https://github.com/nuxt/content/releases/tag/v3.8.1. We would need to update the @nuxt/content peer dependency to 3.8.1 as well right?

@danielroe
Copy link
Member Author

once I merge nuxt/nuxt#33689, we should be fine with the latest nuxt patch even if uses don't update content

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants