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.
This pull request introduces a bug fix release (v2.2.2-stage.1) focused on improving Nuxt content API request handling and ensuring better Node.js compatibility in edge environments. The two main themes are routing enhancements for Nuxt content APIs and the addition of a polyfill for Node.js console timing functions.
Nuxt content API routing improvements:
config.tsto handle requests starting with/api/_content, ensuring that Nuxt function execution and correct cookie forwarding/delivery occur for @nuxt/content API endpoints.Node.js compatibility/polyfills:
consoleobject, specifically supportingconsole.timeandconsole.timeEnd, to the Unenv preset by introducingconsole.jsand updating the exports inindex.ts. [1] [2]