Seeking Feedback on CORS Behavior of FetchHttpClient in Effect Typescript Library
Cross-posting my issue regarding CORS behaviour of FetchHttpClient here to ensure I'm not using it wrong and that this is expected behaviour:
🚀-beginners
If you agree that this is a bug, I can open a GitHub issue for it
a workaround is to wrap fetch() in tryPromise, but I really like the HttpClient API, it's very well designed IMO
🚀-beginners
If you agree that this is a bug, I can open a GitHub issue for it
a workaround is to wrap fetch() in tryPromise, but I really like the HttpClient API, it's very well designed IMO
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
