if `wrangler dev` is the right command this is the error I'm getting: ``` [wrangler:inf] Ready on h

Mmr nooli if `wrangler dev` is the right command this is the error I'm getting: ``` [wran...

H

It should be

wrangler pages dev

wrangler pages dev

instead

H

Hello, I’m Allie!•3/24/24, 4:33 PM

Since it is Pages

M

mr nooliOP•3/24/24, 4:35 PM

ah, doing that gives me:

node_modules/wrangler/wrangler-dist/cli.js:29573
            throw a;
            ^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.

node_modules/wrangler/wrangler-dist/cli.js:29573
            throw a;
            ^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.

node_modules/wrangler/wrangler-dist/cli.js:29573
            throw a;
            ^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.

node_modules/wrangler/wrangler-dist/cli.js:29573
            throw a;
            ^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.

M

mr nooliOP•3/24/24, 4:38 PM

oh wait that was cos the port was in use, forcing a port just gives me a 404 error

M

mr nooliOP•3/24/24, 4:38 PM

do I need to include a

node-compat

node-compat

node-compat

node-compat somewhere?

J

James•3/24/24, 4:41 PM

npx wrangler pages dev .vercel/output/static --compatibility-flag=nodejs_compat

npx wrangler pages dev .vercel/output/static --compatibility-flag=nodejs_compat

npx wrangler pages dev .vercel/output/static --compatibility-flag=nodejs_compat

npx wrangler pages dev .vercel/output/static --compatibility-flag=nodejs_compat

J

James•3/24/24, 4:41 PM

muscle memory

M

mr nooliOP•3/24/24, 4:43 PM

legend, how do I load my environment variables from that

J

James•3/24/24, 4:45 PM

I think wrangler uses .dev.vars instead of .env, which drives me absolutely crazy

M

mr nooliOP•3/24/24, 4:45 PM

M

mr nooliOP•3/24/24, 4:46 PM

oh it's workign

M

mr nooliOP•3/24/24, 4:46 PM

no errors locally

M

mr nooliOP•3/24/24, 4:46 PM

J

James•3/24/24, 4:47 PM

lol perfect

M

mr nooliOP•3/24/24, 4:47 PM

✘ [ERROR] Your worker created multiple branches of a single stream (for instance, by calling `response.clone()` or `request.clone()`) but did not read the body of both branches. This is wasteful, as it forces the system to buffer the entire stream of data in memory, rather than streaming it through. This may cause your worker to be unexpectedly terminated for going over the memory limit. If you only meant to copy the request or response headers and metadata (e.g. in order to be able to modify them), use the appropriate constructors instead (for instance, `new Response(response.body, response)`, `new Request(request)`, etc).

✘ [ERROR] Your worker created multiple branches of a single stream (for instance, by calling `response.clone()` or `request.clone()`) but did not read the body of both branches. This is wasteful, as it forces the system to buffer the entire stream of data in memory, rather than streaming it through. This may cause your worker to be unexpectedly terminated for going over the memory limit. If you only meant to copy the request or response headers and metadata (e.g. in order to be able to modify them), use the appropriate constructors instead (for instance, `new Response(response.body, response)`, `new Request(request)`, etc).

✘ [ERROR] Your worker created multiple branches of a single stream (for instance, by calling `response.clone()` or `request.clone()`) but did not read the body of both branches. This is wasteful, as it forces the system to buffer the entire stream of data in memory, rather than streaming it through. This may cause your worker to be unexpectedly terminated for going over the memory limit. If you only meant to copy the request or response headers and metadata (e.g. in order to be able to modify them), use the appropriate constructors instead (for instance, `new Response(response.body, response)`, `new Request(request)`, etc).

✘ [ERROR] Your worker created multiple branches of a single stream (for instance, by calling `response.clone()` or `request.clone()`) but did not read the body of both branches. This is wasteful, as it forces the system to buffer the entire stream of data in memory, rather than streaming it through. This may cause your worker to be unexpectedly terminated for going over the memory limit. If you only meant to copy the request or response headers and metadata (e.g. in order to be able to modify them), use the appropriate constructors instead (for instance, `new Response(response.body, response)`, `new Request(request)`, etc).

(?) could this be the issue?

J

James•3/24/24, 4:48 PM

nah that's an annoying warning because of a response.clone in react i think it is

J

James•3/24/24, 4:48 PM

or it's a request.clone that they do somewhere, can't remember. i just recall dario found the line in react where it comes from

M

mr nooliOP•3/24/24, 4:49 PM

hmmmm any idea what the 1101 error could be from/how to debug it?

J

James•3/24/24, 4:49 PM

that would suggest an error is being thrown IIRC, you could tail a deployment and see if there's any useful logs?

M

mr nooliOP•3/24/24, 4:49 PM

what's the command for that?

J

James•3/24/24, 4:50 PM

npx wrangler pages deployment tail

npx wrangler pages deployment tail

npx wrangler pages deployment tail

npx wrangler pages deployment tail

M

mr nooliOP•3/24/24, 4:51 PM

I can't login (?)

M

mr nooliOP•3/24/24, 4:52 PM

Successfully logged in.
Expired! Auth code or refresh token needs to be renewed.
/Volumes/Primary/Code/cms/node_modules/wrangler/wrangler-dist/cli.js:29573
            throw a;
            ^

ErrorInvalidGrant

Successfully logged in.
Expired! Auth code or refresh token needs to be renewed.
/Volumes/Primary/Code/cms/node_modules/wrangler/wrangler-dist/cli.js:29573
            throw a;
            ^

ErrorInvalidGrant

Successfully logged in.
Expired! Auth code or refresh token needs to be renewed.
/Volumes/Primary/Code/cms/node_modules/wrangler/wrangler-dist/cli.js:29573
            throw a;
            ^

ErrorInvalidGrant

Successfully logged in.
Expired! Auth code or refresh token needs to be renewed.
/Volumes/Primary/Code/cms/node_modules/wrangler/wrangler-dist/cli.js:29573
            throw a;
            ^

ErrorInvalidGrant

M

mr nooliOP•3/24/24, 4:52 PM

browser sends me to localhost and then I get a localhost refuses to connect

M

mr nooliOP•3/24/24, 4:54 PM

ok strange apparently arc blocks that for some reason

J

James•3/24/24, 4:54 PM

lol

M

mr nooliOP•3/24/24, 4:54 PM

works in safari tho

JJames `npx wrangler pages deployment tail`

M

mr nooliOP•3/24/24, 4:55 PM

how do you specify the deployment for preview?

J

James•3/24/24, 4:55 PM

it will choose the latest deployment by default

J

James•3/24/24, 4:56 PM

here ya go

M

mr nooliOP•3/24/24, 4:56 PM

ahhh you legend

M

mr nooliOP•3/24/24, 4:57 PM

this hurts me

J

James•3/24/24, 4:58 PM

well that isn't what i wanted to see XD

M

mr nooliOP•3/24/24, 4:58 PM

M

mr nooliOP•3/24/24, 4:59 PM

I've got to run off and do something else rn, but I'll be back in a couple hours

hopefully the magic

will have fixed it by the time I'm back, otherwise I'll create an issue in

pages-help

pages-help

pages-help

pages-help

J

James•3/24/24, 5:00 PM

huh, odd, requests to _next/image are throwing an exception

J

James•3/24/24, 5:00 PM

that is pretty strange

M

mr nooliOP•3/24/24, 5:00 PM

On my website?

J

James•3/24/24, 5:00 PM

Yes

M

mr nooliOP•3/24/24, 5:00 PM

:0

J

James•3/24/24, 5:01 PM

Could you try a deployment with 1.10.0 by any chance? See if there might be a regression in 1.11.0?

J

James•3/24/24, 5:01 PM

and if 1.10.0 works, try 1.11.0 again just for the sake of it

M

mr nooliOP•3/24/24, 5:01 PM

Kk I’ll give it a go once I’m back

M

mr nooliOP•3/24/24, 5:02 PM

Cheers @James

J

James•3/24/24, 5:02 PM

no worries

JJames Could you try a deployment with 1.10.0 by any chance? See if there might be a re...

M

mr nooliOP•3/24/24, 8:38 PM

1.10.0 works

J

James•3/24/24, 8:38 PM

now please try 1.11.0 again just to confirm

M

mr nooliOP•3/24/24, 9:04 PM

so

M

mr nooliOP•3/24/24, 9:04 PM

that also works

M

mr nooliOP•3/24/24, 9:04 PM

if `wrangler dev` is the right command this is the error I'm getting: ``` [wrangler:inf] Ready on h

Similar Threads

Similar Threads

Similar Threads