Hey folks, just a bit of feedback, I spent 4-5 hours just trying to get a working setup for wrangler

Hey folks, just a bit of feedback, I spent 4-5 hours just trying to get a working setup for wrangler and Cloudflare Pages inside Github Codespaces. All sorts of linux package dependency incompatibilities (e.g.

libc++1

libc++1

libc++1

libc++1,

libunwind

libunwind

libunwind

libunwind), and then I had to resort to using

wrangler@beta

wrangler@beta

wrangler@beta

wrangler@beta in order for things to work out.
I know

workerd

workerd

is being actively worked on, but hopefully this will get more smooth down the line since the local DX is a bit annoying to having to sort out every few months...

Llambrospetrou Hey folks, just a bit of feedback, I spent 4-5 hours just trying to get a workin...

James•7/4/23, 1:08 PM

Yep thankfully

wrangler@beta

wrangler@beta

resolves most of the dependency issues and unblocks many people now. There’s still a few regressions from v2, but it’s slowly getting there.

Wrangler 3 was a pretty rough experience for a lot of people, and the wrangler team has been made very aware of this.

I too am hopeful that better testing internally is a much stronger focus moving forward.

kian•7/4/23, 4:21 PM

Is your workers-types up to date?

kian•7/4/23, 4:54 PM

Ah, it's been fixed but not yet released

Cyb3r-Jak3•7/6/23, 1:48 AM

Has anyone else seen this error before?

FATAL ERROR: v8::ToLocalChecked Empty MaybeLocal.
 1: 0xb090e0 node::Abort() [node]
 2: 0xa1b60e node::FatalError(char const*, char const*) [node]
 3: 0xce178a v8::Utils::ReportApiFailure(char const*, char const*) [node]
 4: 0xb22165  [node]
 5: 0x1a68837 llhttp__internal_execute [node]
 6: 0xb252ad  [node]
 7: 0xbe50dd node::LibuvStreamWrap::OnUvRead(long, uv_buf_t const*) [node]
 8: 0xbe54c4  [node]
 9: 0x1558427  [node]
10: 0x1558c50  [node]
11: 0x155ee34  [node]
12: 0x154d058 uv_run [node]
13: 0xa43975 node::SpinEventLoop(node::Environment*) [node]
14: 0xbc7692 node::worker::Worker::Run() [node]
15: 0xbc7e28  [node]
16: 0x7f110c5a9b43  [/lib/x86_64-linux-gnu/libc.so.6]
17: 0x7f110c63ba00  [/lib/x86_64-linux-gnu/libc.so.6]
Aborted (core dumped)

FATAL ERROR: v8::ToLocalChecked Empty MaybeLocal.
 1: 0xb090e0 node::Abort() [node]
 2: 0xa1b60e node::FatalError(char const*, char const*) [node]
 3: 0xce178a v8::Utils::ReportApiFailure(char const*, char const*) [node]
 4: 0xb22165  [node]
 5: 0x1a68837 llhttp__internal_execute [node]
 6: 0xb252ad  [node]
 7: 0xbe50dd node::LibuvStreamWrap::OnUvRead(long, uv_buf_t const*) [node]
 8: 0xbe54c4  [node]
 9: 0x1558427  [node]
10: 0x1558c50  [node]
11: 0x155ee34  [node]
12: 0x154d058 uv_run [node]
13: 0xa43975 node::SpinEventLoop(node::Environment*) [node]
14: 0xbc7692 node::worker::Worker::Run() [node]
15: 0xbc7e28  [node]
16: 0x7f110c5a9b43  [/lib/x86_64-linux-gnu/libc.so.6]
17: 0x7f110c63ba00  [/lib/x86_64-linux-gnu/libc.so.6]
Aborted (core dumped)

I am using

unstable_dev

unstable_dev

and only getting this error when running in GitHub actions and not locally

DaniFoldi•7/6/23, 5:44 AM

Is this on node 16?

Jökull Sólberg•7/6/23, 7:32 AM

I am using Vercel CI for Next and wrangler to deploy my worker. Vercel takes 3.5 minutes and wrangler 30 seconds. Is there a way to synchronize their deployment or do I have to do this in 3 steps - a) deploy future compatible backend, 2) deploy frontend, 3) (optional) deploy deprecations for backend

I'd like to keep the Vercel CI if possible, It's quite nice. I also don't think next-on-pages is ready, but might be willing to give that a try again if it's progressed massively. Last I checked I couldn't access bindings and env

James•7/6/23, 9:08 AM

To add to that, bindings can be accessed via

process.env

process.env

and will be available when running through wrangler/deployed. In next dev, you could try using a proxy like https://github.com/james-elicx/cf-bindings-proxy

Jökull Sólberg•7/6/23, 9:10 AM

Oh wow ... this should be useful for SvelteKit too -- right?

JJökull Sólberg Oh wow ... this should be useful for SvelteKit too -- right?

James•7/6/23, 9:16 AM

I've never used svelte before so I wouldn't be able to say. This falls back to

process.env

process.env

in prod builds - if svelte uses that then yes. if not, i suppose it could probably be modified to accept a second parameter so that you can also pass in a custom variable to fallback to instead of

process.env

process.env

Jökull Sólberg•7/6/23, 9:17 AM

Reading next-on-pages --- not seeing information on how to use schedule and queue. I'm using that. Is there a way to use Pages to deploy this thing, but still have

export default {fetch,queue,schedule}

export default {fetch,queue,schedule}

JJökull Sólberg Reading next-on-pages --- not seeing information on how to use schedule and queu...

James•7/6/23, 9:24 AM

Pages doesn't support using those two - you should have a separate worker for them. Even if Pages did support them, there would not be a way to use them with NOP at the moment

Jökull Sólberg•7/6/23, 9:31 AM

My issue is mainly synchronous deployment. There's a drift of 2 minutes because of the CI difference (nice job on that btw ... workers deploy FAST)

Jökull Sólberg•7/6/23, 9:31 AM

It's not a massive issue - we'll launch and live with it. Just have to manually orchestrate migrations and deployments etc.

Laurent Pellegrino•7/6/23, 6:55 PM

When running

wrangler deploy

wrangler deploy

I am suddenly getting :

✘ [ERROR] A request to the Cloudflare API (/zones) failed.

An unknown API error occurred. [code: 500]

Any ongoing issue?

Laurent Pellegrino•7/6/23, 6:55 PM

after the fourth run it seems to work again...

Saulo Vallory•7/6/23, 8:25 PM

Hey guys! How are you?

I've been trying since yesterday to properly setup a pages deploy using wrangler. I just got it to deploy, but the variables and other configurations I've defined in

wrangler.toml

wrangler.toml

were not applied

I've read basically everything in the docs. Does anyone have an idea of what the issue might be?

SSaulo Vallory Hey guys! How are you? I've been trying since yesterday to properly setup a pag...

Hello, I’m Allie!•7/6/23, 8:28 PM

Pages requires all config to be applied from the dash. It doesn’t respect wrangler.toml

Hello, I’m Allie!•7/6/23, 8:28 PM

That it sometimes does in dev is a bug

Saulo Vallory•7/6/23, 8:40 PM

oh boy....

Saulo Vallory•7/6/23, 8:40 PM

thank you so much, @HardAtWork ! I would have never guessed. That should be in very big letters in the docs :/

Tin Cap•7/6/23, 9:33 PM

Where are the current miniflare docs? https://miniflare.dev seems to be the old version. I didn't see anything in the Cloudflare docs around https://developers.cloudflare.com/workers/wrangler/commands/#dev

I just upgraded a project from Wrangler 2 to 3, so I'm looking to seed my local KV with data.

TTin Cap Where are the current miniflare docs? https://miniflare.dev seems to be the old ...

Hello, I’m Allie!•7/6/23, 9:36 PM

IIRC, Miniflare@>3 and onwards loses most of the local API

Hello, I’m Allie!•7/6/23, 9:36 PM

Because it is being more of a middle-layer between

wrangler

wrangler

workerd

workerd

, rather than a full-blown emulator

HHello, I’m Allie!IIRC, Miniflare@>3 and onwards loses most of the local API

Tin Cap•7/6/23, 9:38 PM

Hmm, the wrangler dev documentation explains a bit about persisting local data.

I found this page, but it doesn't really explain how to use Miniflare much. https://developers.cloudflare.com/workers/learning/debugging-workers/#local-testing-with-wrangler-dev

TTin Cap Hmm, the wrangler dev documentation explains a bit about persisting local data. ...

Hello, I’m Allie!•7/6/23, 9:41 PM

Yeah, so basically, at the moment, wrangler will persist your data locally, but afaik, there isn’t a way of seeding it, short of running another Worker to do so

HHello, I’m Allie!Yeah, so basically, at the moment, wrangler will persist your data locally, but ...

Tin Cap•7/6/23, 9:50 PM

I currently have a directory in my repo of

.wrangler/state/kv/<KV_BINDING>/...

.wrangler/state/kv/<KV_BINDING>/...

where I have seeded data for local testing, but that's with wrangler v2. Sure would be nice to have something similar for wrangler v3. My worker uses KV as a read-only DB (writing happens outside my worker), so I don't have way to get data into KV for testing unless I wrote something specific to do that, which is not the end of the world I suppose.

CCendyne wrangler-action support wrangler3 (#108) PR closed without merged commits?

Cyb3r-Jak3•7/6/23, 9:52 PM

See https://github.com/cloudflare/wrangler-action/discussions/111

Tin Cap•7/6/23, 10:28 PM

I think I'm going to downgrade back to Wrangler v2. Losing local persistence for seeding data and losing the miniflare v2 api is pretty painful. The docs for wrangler are for v2 and the miniflare 3 docs don't really exist. It feels kinda premature to move to wrangler 3. I know there is some feedback already about the transition being rough, but it's not very smooth for me either. Just some feedback from my experience so far trying wrangler 3.