Skip to content
New issue

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

CORS + Response body object should not be disturbed or locked #11910

Open
Bobetti opened this issue Jul 31, 2024 · 3 comments
Open

CORS + Response body object should not be disturbed or locked #11910

Bobetti opened this issue Jul 31, 2024 · 3 comments

Comments

@Bobetti
Copy link

Bobetti commented Jul 31, 2024

Everything trying on local machine: Windows 10, Vercel CLI 35.2.2, node v21.7.1 Using Visual Studio Code

On the http://localhost:5001/ i have sveltkit application fetching my server

image

Server is running http://localhost:3000/
Code with honojs looks like this:

image

If from client side headers and body are present, when I get the error on the client side:

image

and on the server:

image

and log to console on server side: POST: api/pricing---> never hit

If I comment out headers and body:

image

when no errors on both sides.

Package json looks like this:

image

Found similar topics with CORS problems: #10927

but downgrade to vercel cli to version 32.0.1 didn't help:
still get: TypeError: Response body object should not be disturbed or locked

Thank you for your help

P.S. Created the cloudflare worker with the exact honojs code - and everything works fine. So it means, that the problem is not in Hono.js

@Bobetti
Copy link
Author

Bobetti commented Aug 1, 2024

Up

@JBeaudaux
Copy link

Same problem here

@Zertsov
Copy link
Contributor

Zertsov commented Feb 26, 2025

@Bobetti Hey! Is this still happening on the latest version of the CLI? Also, could you provide a barebones repo for us to use to try and reproduce?

I'm wondering if this has anything to do with the CLI and just wanna make sure we route this to the right spot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants