https://developer.mozilla.org/en-US/docs/Web/API/Request

S

StrikeOP•7/28/22, 10:36 PM

not spec compliant

K

kian•7/28/22, 10:36 PM

What isn't spec compliant?

S

StrikeOP•7/28/22, 10:36 PM

console.log(req) just returns any empty object

K

kian•7/28/22, 10:36 PM

What makes you think that isn't spec compliant?

K

kian•7/28/22, 10:37 PM

You'll get the same in any browser's console that I know of

S

StrikeOP•7/28/22, 10:37 PM

no

S

StrikeOP•7/28/22, 10:37 PM

S

StrikeOP•7/28/22, 10:37 PM

T

TheSunSide•7/28/22, 10:37 PM

The Chrome browser will show all "JSON" attributes

SStrike Click to see attachment

S

StrikeOP•7/28/22, 10:39 PM

like is that something with console.log?

U

Unsmart•7/28/22, 10:39 PM

I dont think the spec defines how something should be logged out in console though tbh

so does it really make request not complaint

T

TheSunSide•7/28/22, 10:39 PM

The only way it worked for me to do something similar is with the JSON.stringify

T

TheSunSide•7/28/22, 10:39 PM

Might be because of the readonly attributes

TTheSunSide Try JSON.stringify(req)

K

kian•7/28/22, 10:39 PM

I was referring to this personally

K

kian•7/28/22, 10:39 PM

console.log(request)

console.log(request)

console.log(request)

console.log(request) works fine in Workers

K

kian•7/28/22, 10:39 PM

S

StrikeOP•7/28/22, 10:39 PM

why doesn't it work for me tho

S

StrikeOP•7/28/22, 10:40 PM

like it's just

console.log(new Request("https://example.com"))

console.log(new Request("https://example.com"))

console.log(new Request("https://example.com"))

console.log(new Request("https://example.com"))

K

kian•7/28/22, 10:41 PM

K

kian•7/28/22, 10:41 PM

Going to need more of your Worker's code if that's what you're doing & it isn't working

S

StrikeOP•7/28/22, 10:41 PM

export default {
    fetch: (req: Request, env: any, ctx: any) => {
        console.log(new Request("https://example.com"));
        return new Response(JSON.stringify({ abc: "hello" }), {
            status: 200,
        });
    },
};

export default {
    fetch: (req: Request, env: any, ctx: any) => {
        console.log(new Request("https://example.com"));
        return new Response(JSON.stringify({ abc: "hello" }), {
            status: 200,
        });
    },
};

export default {
    fetch: (req: Request, env: any, ctx: any) => {
        console.log(new Request("https://example.com"));
        return new Response(JSON.stringify({ abc: "hello" }), {
            status: 200,
        });
    },
};

export default {
    fetch: (req: Request, env: any, ctx: any) => {
        console.log(new Request("https://example.com"));
        return new Response(JSON.stringify({ abc: "hello" }), {
            status: 200,
        });
    },
};

S

StrikeOP•7/28/22, 10:43 PM

^ logs to the console

Request {

}

Request {

}

Request {

}

Request {

}

K

kian•7/28/22, 10:43 PM

K

kian•7/28/22, 10:43 PM

Works fine for me personally

S

StrikeOP•7/28/22, 10:43 PM

using miniflare logs it to the console

K

kian•7/28/22, 10:44 PM

That'll be a question for #miniflare - it works fine in Workers itself

S

StrikeOP•7/28/22, 10:44 PM

what

S

StrikeOP•7/28/22, 10:44 PM

using miniflare logs it

S

StrikeOP•7/28/22, 10:44 PM

wrangler dev

wrangler dev

doesn't

T

TheSunSide•7/28/22, 10:45 PM

wrangler tail ?

T

TheSunSide•7/28/22, 10:45 PM

oh you're previewing on the edge

S

StrikeOP•7/28/22, 10:56 PM

welp

K

kian•7/28/22, 11:03 PM

console.log

console.log

being

console.log

console.log

the Workers API objects stop being 'loggable' by
```
console.log
```
```
console.log
```
when
```
workers_api_getters_setters_on_prototype
```
workers_api_getters_setters_on_prototype
```
workers_api_getters_setters_on_prototype
```
workers_api_getters_setters_on_prototype
is defined or the compatibility date is
```
2022-01-31
```
2022-01-31
```
2022-01-31
```
2022-01-31
or later.

K

kian•7/28/22, 11:03 PM

I don't think it's particularly a bug or something that they'll be in a hurry to change.

Kkian `console.log` being `console.log` - the Workers API objects stop being 'loggable...

S

StrikeOP•7/28/22, 11:04 PM

ah, it's the latter then

Kkian `console.log` being `console.log` - the Workers API objects stop being 'loggable...

S

StrikeOP•7/28/22, 11:05 PM

so after

2022-01-31

2022-01-31

2022-01-31

2022-01-31 how would you log the Request object then if Workers API objects stop being 'loggable' kek

?

S

StrikeOP•7/28/22, 11:09 PM

would it just to call them all manually?

S

StrikeOP•7/28/22, 11:10 PM

that's fine, sorry I don't log my request often and I was just testing something(I didn't realize that my compat date was set to 2022-04-05

J

James•7/28/22, 11:12 PM

You'd just iterate over the parts you care to log, yeah. You could probably find all the available stuff via

Object.keys(new Request('https://example.com').__proto__)

Object.keys(new Request('https://example.com').__proto__)

Object.keys(new Request('https://example.com').__proto__)

Object.keys(new Request('https://example.com').__proto__) or something though. What's your use for logging the entire thing?

DDayDreaming @Unsmart | Tech debt Sorry to bother you... looking at your example (chatroom) :...

U

Unsmart•7/28/22, 11:39 PM

You need a worker to send the traffic to the DO yes, but you can connect a websocket and once your connected as a websocket you can message the DO freely as if theres not any worker because the websocket will be on the DO directly.

U

Unsmart•7/28/22, 11:40 PM

https://github.com/cloudflare/workers-chat-demo/blob/b4462b1be2dd110c313ed7c9baed92044e03181c/src/chat.mjs#L238-L259

GitHub

workers-chat-demo/chat.mjs at b4462b1be2dd110c313ed7c9baed92044e031...

Contribute to cloudflare/workers-chat-demo development by creating an account on GitHub.

U

Unsmart•7/28/22, 11:41 PM

Yes, for any timed events you can use alarms. So if you need to do something in 30s you state.storage.setAlarm(Date.now() + 1000 * 30)

U

Unsmart•7/28/22, 11:41 PM

and it will call an alarm handler

CChaika Just non-descript error page In console the only thing that seems relevant is ...

R

relates•7/29/22, 8:00 AM

just hit this snag too, you can't edit any custom domain too, getting this particular error. can you do this on cli?

My custom domain isn't working though, unlike Chaika

https://developer.mozilla.org/en-US/docs/Web/API/Request

Similar Threads

Similar Threads

Similar Threads