feat: add compatibility date support #2511
Merged
Conversation
This file contains 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
pi0
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Compatibility dates allow Nitro presets to update their behavior in non-semver-major releases of Nitro (and higher order toolings as well).
This PR adds support for
compatibilityDateoption in nitro config which will be required and with a warning, we ask users to set it.See compatx and this RFC for more context.
When no compatibility date is specified, we assume latest stable release v2.9.6 as safe fallback and show guide to update:
Auto update wizard:
With Nitro CLI: (nitro dev only)
No prompt (nuxt CLI, nitro build, user canceled, etc)
--
Note: Framework authors can inspire from this utility to implement auto update flow.