fix(nuxt): mark non-augmented NuxtApp properties as unknown #19643
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.
π Linked issue
resolves #14495
β Type of change
π Description
This adds more typings for internal NuxtApp properties, primarily for our own internal use. None of the properties marked as
@internal
should be relied on by end users.It also updates the default typing of unknown properties on NuxtApp to
unknown
meaning it will properly respect end users' strictness settings and flag issues when the type is missing (for example, if a provided property is renamed).π Checklist