Strange issue with `console.log()` omitting members of objects

I'm using Itty Router with CF Workers. For some reason, when working locally and I run

console.log(req)

console.log(req)

console.log(req)

console.log(req) (in middleware, obviously) the vast majority of the members of that object are not shown.

For example, if I run:

console.log(req)

console.log(req)

console.log(req)

console.log(req)

...all I get logged is:

Request {
  query: Object,
  params: Object,
  route: *,
  content: Object
}

Request {
  query: Object,
  params: Object,
  route: *,
  content: Object
}

Request {
  query: Object,
  params: Object,
  route: *,
  content: Object
}

Request {
  query: Object,
  params: Object,
  route: *,
  content: Object
}

However, if I run:

console.log(req.keepalive)

console.log(req.keepalive)

console.log(req.keepalive)

console.log(req.keepalive)

...I get:

false

false

false

false

That's just one example of missing data. There's also a

Headers

Headers

Headers

Headers object that I know is there because I can call

req.headers.get('my-header')

req.headers.get('my-header')

req.headers.get('my-header')

req.headers.get('my-header') and it works.

Any thoughts as to what's going on here?

kian•4/17/24, 5:06 PM

query, params, route, etc aren’t part of any CF request object I know about

kian•4/17/24, 5:06 PM

Is this with a routing library?

MityaOP•4/17/24, 5:06 PM

I mentioned I was using Itty Router

Kevin•4/17/24, 5:25 PM

@Mitya I have a bit more thorough description on your post in the Itty Discord, but I think the culprit is the weirdness in your export signature... you're basically creating and calling fetch on instantiation, which is sending a non-request through the router. Thus you only see the props that itty adds, and nothing from a real request.

MityaOP•4/18/24, 10:49 AM

Thank you, @Kevin | itty.dev , I'll reply over on the Itty server

Strange issue with `console.log()` omitting members of objects

Similar Threads

Similar Threads

Similar Threads