should be the same, 16 or greater

JJacobMGEvans should be the same, 16 or greater

H

hanpolo•6/10/23, 4:41 AM

So this is good enough for workerd

Mmv Getting inconsistent behavior on `wrangler pages dev`. sometimes `localhost:8788...

J

JacobMGEvansOP•6/10/23, 4:41 AM

please make an issue in the Workers-SDK repo, https://github.com/cloudflare/workers-sdk

H

hanpolo•6/10/23, 4:42 AM

I've got the issue already. It's been out a few days, and I was trying to make progress on it .. so thought perhaps it is node

Hhanpolo So this is good enough for workerd

J

JacobMGEvansOP•6/10/23, 4:42 AM

Are you running across issues Hanpolo?

H

hanpolo•6/10/23, 4:42 AM

https://github.com/cloudflare/workers-sdk/issues/3408

GitHub

🐛 BUG: wrangler pages dev, trying to start localhost:8788 crashes ·...

Which Cloudflare product(s) does this pertain to? Pages, Wrangler What version of Wrangler are you using? 3.0.1 What operating system are you using? Mac OS 13.2.1 Describe the Bug I upgraded to Wra...

H

hanpolo•6/10/23, 4:43 AM

Basically been fully stuck and unable to upgrade for several days

Hhanpolo https://github.com/cloudflare/workers-sdk/issues/3408

J

JacobMGEvansOP•6/10/23, 4:48 AM

@walshydev For monday to look at, seems like a problem a lot of people are having

J

JacobMGEvansOP•6/10/23, 4:48 AM

I will look into this Monday as well.

H

hanpolo•6/10/23, 4:54 AM

Thank you so much ... let me know if I can help in any way. Note that I've included iinstructions & github repo to help reproduce the bug.

K

kian•6/11/23, 5:59 PM

Module Workers (

export default

export default

) don't have bindings as globals, it's under

env

env

which is the 2nd argument passed to a handler

K

kian•6/11/23, 5:59 PM

export default {
  async fetch(req, env, ctx) {
    // ...
    console.log(env.TOKEN);
    // ...
  }
}

export default {
  async fetch(req, env, ctx) {
    // ...
    console.log(env.TOKEN);
    // ...
  }
}

export default {
  async fetch(req, env, ctx) {
    // ...
    console.log(env.TOKEN);
    // ...
  }
}

export default {
  async fetch(req, env, ctx) {
    // ...
    console.log(env.TOKEN);
    // ...
  }
}

J

James•6/11/23, 6:07 PM

wrangler dev

wrangler dev

in wrangler 3 uses a local version of

workerd

workerd

workerd

workerd by default, which is very limited in terms of the OS versions it supports unfortunately.

J

James•6/11/23, 6:07 PM

--remote

--remote

runs your code on a remote Cloudflare controlled server, so it's a bit slower, but you avoid the need for local

workerd

workerd

workerd

workerd

J

James•6/11/23, 6:08 PM

I would definitely file an issue https://github.com/cloudflare/workers-sdk/issues with your OS version and things though so workerd can work in your environment

J

James•6/11/23, 6:08 PM

If you absolutely need to run local, you could downgrade to

wrangler@2

wrangler@2

wrangler@2

wrangler@2 for now, which uses a more simulated local environment with node.js

G

gonz•6/12/23, 8:47 AM

anyone know how to specify zone ID/name when using

npx wrangler deploy

npx wrangler deploy

npx wrangler deploy

npx wrangler deploy (without

-e

-e

-e

-e)?

Ggonz anyone know how to specify zone ID/name when using `npx wrangler deploy` (withou...

H

Hello, I’m Allie!•6/12/23, 8:48 AM

With wrangler.toml/.json?

HHello, I’m Allie!With wrangler.toml/.json?

G

gonz•6/12/23, 8:50 AM

basically what I'm trying to do is add a custom route + name for the worker during the CI pipeline... I know I can add it to wrangler.toml, but that would mean that during CI, I'd have to add the environment to the file before running wrangler (was hoping to do it all with CLI args)

G

gonz•6/12/23, 8:50 AM

currently I've got

npx wrangler deploy --route '<custom path>/*' --name <dynamic name>

npx wrangler deploy --route '<custom path>/*' --name <dynamic name>

npx wrangler deploy --route '<custom path>/*' --name <dynamic name>

npx wrangler deploy --route '<custom path>/*' --name <dynamic name> but it's complaining that I didn't specify a zone ID or name

Ggonz currently I've got `npx wrangler deploy --route '<custom path>/*' --name <dynami...

H

Hello, I’m Allie!•6/12/23, 8:53 AM

Just to verify, does your

<custom path>

<custom path>

<custom path>

<custom path> value contain a hostname? Like

example.com/*

example.com/*

example.com/*

example.com/*? Or just a path?

HHello, I’m Allie!Just to verify, does your `<custom path>` value contain a hostname? Like `exampl...

G

gonz•6/12/23, 9:00 AM

Yes contains hostname

G

gonz•6/12/23, 9:09 AM

It's actually <subdomain>.<cloudflare zone>/*

M

mukhtharcm•6/12/23, 9:11 AM

Hi,
I'm getting a weird error today.
I upgraded from windows 10 to windows 11 and I'm getting this error when trying to run anything

Error: write EOF
    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -4095,
  code: 'EOF',
  syscall: 'write'
}

Error: write EOF
    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -4095,
  code: 'EOF',
  syscall: 'write'
}

Error: write EOF
    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -4095,
  code: 'EOF',
  syscall: 'write'
}

Error: write EOF
    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -4095,
  code: 'EOF',
  syscall: 'write'
}

M

mukhtharcm•6/12/23, 9:11 AM

Any Idea?

G

gonz•6/12/23, 10:01 AM

@HardAtWork the misleading error message about having to specify zone ID or name was because the

.env

.env

file with my Cloudflare API token went missing

all OK now

Mmukhtharcm Hi, I'm getting a weird error today. I upgraded from windows 10 to windows 11 a...

J

JacobMGEvansOP•6/12/23, 6:49 PM

Does your Worker write to a file?

Hhanpolo https://github.com/cloudflare/workers-sdk/issues/3408

J

JacobMGEvansOP•6/12/23, 6:51 PM

@walshydev you have any input or someone that can skim the ticket?

J

JacobMGEvansOP•6/12/23, 6:51 PM

Want to just get initial assessment

J

JacobMGEvansOP•6/12/23, 6:51 PM

Seen more than one person mention this, trying to sus out if it's v3 related and how

J

JacobMGEvansOP•6/12/23, 6:52 PM

Maybe... @gregbrimble

W

Walshy•6/12/23, 6:52 PM

Interesting...

W

Walshy•6/12/23, 6:52 PM

@skye_31 any idea what's happening here?

W

Walshy•6/12/23, 6:52 PM

And you're the unofficial pages employee

W

Walshy•6/12/23, 6:54 PM

You're unofficial for a reason LuL

W

Walshy•6/12/23, 6:55 PM

... Bish

W

Walshy•6/12/23, 6:55 PM

Any idea any gzip decompression we do?

JJacobMGEvans Seen more than one person mention this, trying to sus out if it's v3 related and...

G

GregBrimble•6/12/23, 6:56 PM

Definitely v3 related.

kj

kj

kj

kj warnings are from workerd.

G

GregBrimble•6/12/23, 6:57 PM

https://github.com/cloudflare/workers-sdk/blob/05099f4c9ff1f57d62db5b73a8aea73d1ab1aac6/packages/pages-shared/asset-server/handler.ts#L479

GitHub

workers-sdk/handler.ts at 05099f4c9ff1f57d62db5b73a8aea73d1ab1aac6 ...

Home to Wrangler, the CLI for Cloudflare Workers® - workers-sdk/handler.ts at 05099f4c9ff1f57d62db5b73a8aea73d1ab1aac6 · cloudflare/workers-sdk

G

GregBrimble•6/12/23, 6:57 PM

This is the only manual encoding stuff we do that I’m aware of

G

GregBrimble•6/12/23, 6:59 PM

Smells like a workerd bug to me, rather than something Pages-specific

Similar Threads