I just created a new worker using `npm create cloudflare@2` and when starting it it raises the warn/

I just created a new worker using

npm create cloudflare@2

npm create cloudflare@2

npm create cloudflare@2

npm create cloudflare@2 and when starting it it raises the warn/error:

[mf:wrn] The latest compatibility date supported by the installed Cloudflare Workers Runtime is "2023-05-18",
but you've requested "2023-06-14". Falling back to "2023-05-18"...

[mf:wrn] The latest compatibility date supported by the installed Cloudflare Workers Runtime is "2023-05-18",
but you've requested "2023-06-14". Falling back to "2023-05-18"...

[mf:wrn] The latest compatibility date supported by the installed Cloudflare Workers Runtime is "2023-05-18",
but you've requested "2023-06-14". Falling back to "2023-05-18"...

[mf:wrn] The latest compatibility date supported by the installed Cloudflare Workers Runtime is "2023-05-18",
but you've requested "2023-06-14". Falling back to "2023-05-18"...

EEusebio Trigo I just created a new worker using `npm create cloudflare@2` and when starting it...

Cyb3r-Jak3•6/14/23, 11:09 AM

This is a known thing being discussed here: https://github.com/cloudflare/workers-sdk/issues/3363
If you change your compatilibilty date to 2023-05-182023-05-18 it should remove that message. You can also just ignore it

Eusebio TrigoOP•6/14/23, 11:10 AM

I'm ignoring it for now

Aavl Hi I'm trying to deploy a next app with wrangler but at the end of the upload I...

Cyb3r-Jak3•6/15/23, 10:22 AM

Can you share your .pages.dev.pages.dev domain. The staff use it to check their logs

Walshy•6/15/23, 11:14 AM

put: 'Value length of 39837727 exceeds limit of 26214400.'

Walshy•6/15/23, 11:14 AM

the Worker bundle is huge

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

The Function/Worker you're uploading

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

all the associated files with that

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

i see this is next-on-pages, how big is your Next app?

James•6/15/23, 12:16 PM

It's possible you might have really chonky dependencies too that could be replaced with something less chonky

James•6/15/23, 12:25 PM

I mean, you can have large projects, but 40mb is monstrously large. I'm sure there must be some optimizations that could help reduce it

Walshy•6/15/23, 12:29 PM

I mean 40 MB is huge haha

James•6/15/23, 1:17 PM

The maximum worker size? Yes, if you’re ent you can request an upgrade, but I would doubt you’ll get it as high as 40MB honestly

Aavl I removed some of routes and it was deployed successfully, but I have question, ...

James•6/15/23, 1:21 PM

Do you mind if I ask what the routes you removed contained?

AAdam Sorry for the delay getting back to you on this. I'll take a look asap and reply...

Peter Belbin•6/15/23, 2:21 PM

Hey Adam, ummmm, I know you said 'asap', but I'm curious what that actually means? It's now 2 days later, and seems like nothing has happened in GitHub so far.... Thanks in advance!

Phil•6/15/23, 4:48 PM

Using wrangler 3 how do I set up a local DO. Say I wanted to run the chat room demo locally:

https://github.com/cloudflare/workers-chat-demo/blob/master/wrangler.toml

I am finding just running:

npx wrangler dev

When I log "env" I find that it has no keys so it feels like the DO migrations have not been run locally

bindings = [
# { name = "rooms", class_name = "ChatRoom" },
{ name = "lobbies", class_name = "LobbyRoom" },
{ name = "limiters", class_name = "RateLimiter" }
]

[[migrations]]
tag = "v1" # Should be unique for each entry
new_classes = ["ChatRoom", "RateLimiter"]

How do I run so these are available locally?

GitHub

workers-chat-demo/wrangler.toml at master · cloudflare/workers-chat...

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

Phil•6/15/23, 4:56 PM

yes did that env is empty []

Phil•6/15/23, 4:59 PM

do I need

--persist-to
Specify directory to use for local persistence.

I would kind of assume it had a default location.

PPhil do I need --persist-to Specify directory to use for local persistence. I would...

Hello, I’m Allie!•6/15/23, 5:50 PM

What happens if you try to create and then stringify a DO ID? Does it complete?

Phil•6/15/23, 6:07 PM

Thanks working now a line was missing in my wrangler.toml: [durable_objects]

GuillaumeLakano•6/15/23, 6:20 PM

Hi !
With some difficulties ( libc problems ), we've finally successfully be able to uses wrangler 3.x, but the bad news is wrangler 3.x doesn't support Jurisdictions restrictions! :

« Error: Jurisdiction restrictions are not implemented in workerd »

I think this was a bad idea for our case to try to upgrade to 3.x, do we have an ETA of when 3.x will be able to do the same as 2.20.x please?

kian•6/15/23, 6:22 PM

That's for local development

kian•6/15/23, 6:23 PM

I'm not sure if it'll be added in the near-term

GuillaumeLakano•6/15/23, 6:28 PM

Ok, but from what I've read on the blog post about workerd last year ( https://blog.cloudflare.com/workerd-open-source-workers-runtime/ ), the main goal was to have as close as possible the local code with the production code.

But if we uses DO jurisdictions restrictions, the wrangler 2.20.x was more close to the production code, and since 3.x with workerd, I need to do an unsafe « if (env.ENV === 'production') { ... jurisdictions stuff } »

Or may be there is an alternative to have similar code without a blocking error?

Original message was deleted

GuillaumeLakano•6/15/23, 7:08 PM

yes but it's not offline, on a laggy internet connection it's a nightmare to works... we'll go back to wrangler 2.20.x but I hope the dev team will backport fixes & features on 2.x until 3.x will be really able to be better close than production code rather than wrangler 2.x

Erwin•6/16/23, 12:54 AM

Hey devs.. I ran into some issues with developing my Open Telemetry library with a check on the fetchfetch object. Would anyone be able to take a quick look at the issue to see if my proposed solution (change from esbuild defineesbuild define to a Javascript Proxy) doesn't raise any red flags before I start on the PR? https://github.com/cloudflare/workers-sdk/issues/3478

GitHub

🐛 BUG: `checkedFetch` does not support global fetch function which ...

Which Cloudflare product(s) does this pertain to? Wrangler What version of Wrangler are you using? 3.1.0 What operating system are you using? Mac Describe the Bug I am working on an open telemetry ...

Hello, I’m Allie!•6/16/23, 11:26 AM

Is wranglerwrangler supposed to return accurate ageage headers in local dev when using the cache? Atm, it appears to always be age: 0age: 0...

PPeter Belbin Hey Adam, ummmm, I know you said 'asap', but I'm curious what that actually mean...

Adam•6/16/23, 2:47 PM

Hello Peter - thanks for pinging again! I responded here: https://github.com/cloudflare/workers-sdk/pull/3384

It may be next week before a dev can review it, but the team is aware.

MMarty Henderson 👋 Possibly a dumb question - but is there something special that needs to be d...

Hello, I’m Allie!•6/16/23, 3:29 PM

Can you share your code?

AAdam Hello Peter - thanks for pinging again! I responded here: https://github.com/cl...

Peter Belbin•6/16/23, 4:02 PM

Hey Adam, thank you for the progress on that. I'm kinda mystified by something you mentioned in your comment regarding TTL of content in the distributed data centers. If I understand it correctly, you're pointing out that the TTL will be 1 week. But, the TTL I'm concerned about is that for KV assets for the sitesite, specifically the assets that are no longer part of the latest deployed site. Am I correct in thinking they are two different things?

I just created a new worker using `npm create cloudflare@2` and when starting it it raises the warn/

Similar Threads

Similar Threads

Similar Threads