We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After updating workers-types from 4.20240909.0 to 4.20240919.0, a response can no longer use another response as the ResponseInit.
4.20240909.0
4.20240919.0
ResponseInit
Example:
const res1 = new Response('', { headers: { foo: 'bar' } }) const newRes = new Response('hello', res1)
I've used this for ages to inherit headers/etc, as well as make a response mutable.
This also breaks Hono where a common pattern is to do something like this:
const res = await fetch(url) return c.body(res.body, res)
I had to add ts-ignore's to 12 of my Workers to get around this issue :(
The text was updated successfully, but these errors were encountered:
Presumably broken by #2738? @anonrig
Sorry, something went wrong.
It should be fixed by #2755. It seems the latest release doesn't include it yet.
@anonrig No, I think this is a separate bug.
anonrig
workers-devprod
Successfully merging a pull request may close this issue.
After updating workers-types from
4.20240909.0
to4.20240919.0
, a response can no longer use another response as theResponseInit
.Example:
I've used this for ages to inherit headers/etc, as well as make a response mutable.
This also breaks Hono where a common pattern is to do something like this:
I had to add ts-ignore's to 12 of my Workers to get around this issue :(
The text was updated successfully, but these errors were encountered: