refactor: use native Headers
and Response
for legacy polyfills
#523
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
β Type of change
π Description
In h3 1.8, we have changed to rely on native global
Headers
andResponse
objects.To avoid breaking changes, we have kept the (unused)
H3Headers
andH3Response
polyfills in case users by any chance were using them and introduce a breaking change to the exports.Since objects like
Headers
are under development and h3 polyfills lacked many methods includingtoClone()
i think it is just safer to redirect those to native globals as H3 (and Nuxt/Nitro) expect (and polyfill) them anyway and are available in recent versions of Node.js.π Checklist