Comments (4)
Node v18 stopped hiding it's fetch() implementation behind the --experimental-global-fetch
flag. But the fetch() implementation was still a bit buggy. I don't remember what the problem was exactly, looks like fetch() wasn't accepting a Headers object, only a plain object literal.
The solution is to update to a more recent release of Node.js that doesn't have this bug. Fetch is "experimental" until v21, although I'm not aware of any issues with the current LTS v20.
from connect-es.
This is probably bug in the version of undici (the fetch implementation) used by Node.js v18.1. It is not present in v18.0, or v18.2+. BTW, we're running all tests in headless chrome, but also in Node.js v18.2, see the Makefile.
from connect-es.
Ouch, bad version. Will upgrade to the latest Node version and test it out. Closing for now.
from connect-es.
What was the actual problem and/or solution here?
from connect-es.
Related Issues (20)
- Connect serialization should gracefully handle null values HOT 2
- Adding response headers to error responses in interceptor HOT 1
- Allow keeping original method names HOT 2
- Root interceptors are overwritten when service interceptors are also defined HOT 1
- Connect-ES repo cleanup backlog HOT 1
- Error connection: net::ERR_INVALID_HTTP_RESPONSE HOT 2
- Inconsistent debug Field Type in Error Details After connect-go v1.15.0 Update HOT 2
- Documentation: No mention of support for client or bidi streaming HOT 1
- WebTransport transport HOT 3
- RST_STREAM Handling HOT 8
- API Response Omits Properties with Falsy Values HOT 2
- Missing trailers override? HOT 4
- Returning or throwing from a method always triggers an abort HOT 5
- Ping-related error: "session has been destroyed" HOT 2
- Models not exported on Connect package HOT 4
- Not getting all Set-Cookie headers in response when using Node client
- Headers in NodeTransportOptions are not being passed to the request when using createConnectTransport()
- createPromiseClient Not assignable to parameter of type ServiceType HOT 2
- V2: gRPC error code's no longer present in thrown ConnectError HOT 1
- Nodejs Getting started guide is not working HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from connect-es.