Skip to content

Conversation

pi0
Copy link
Member

@pi0 pi0 commented Sep 19, 2023

(context: followup for nuxt/cli#197)

Some Nuxt modules use different major versions for Nuxt compatibility.

This PR adds a new standard compatibility.versionMap (better names welcome) to support mapping compatible Nuxt version to their Corresponding Module compatible version/tag.

@@ -27,3 +27,6 @@ compatibility:
nuxt: ^2.0.0 || ^3.0.0
requires:
bridge: optional
versionMap:
2.x: latest
Copy link
Member

@danielroe danielroe Sep 19, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would it make sense for the map to be [any semver string]: any semver string rather than requiring it to be a tag?

edit: or maybe this is already what you have in mind

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes both sides are semver compatible (righthand is basically whatever npm i pkg@contraint allows)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good for me!

@pi0 pi0 merged commit 2009a01 into main Sep 19, 2023
@pi0 pi0 deleted the feat/module-compat-matrix branch September 19, 2023 10:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants