fix(nuxt): await async callWithNuxt calls
#18443
Merged
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
#15738
β Type of change
π Description
callWithNuxtreturns a promise on server-side, so by not awaiting these instances we ran the risk of getting errors like:Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the clientIn addition,
callWithNuxtwas previously returninganyas its type rather than inferring it based on the input. This fixes that.π Checklist