Cloudflare

Are you able to try deleting and republishing it?

i changed the name in the wrangler.toml which should create another worker and get the same error

Does it at least create the worker successfully?

it is a defferent zone to the workers that work

yes, gets to the "Total uploaded:.." msg and then the error

Send it to `skye@cloudflare.community` 🙂

if I get the `/client/v4/workers/services/worker-name` via postman, I can get the worker

almost thinking its related to https://discord.com/channels/595317990191398933/789155108529111069/1090215388471631884 somehow

Hi team 👋 when following this guide, https://developers.cloudflare.com/workers/platform/sites/start-from-worker/ to configure static assets for Workers with module syntax I keep getting the error; No such module "__STATIC_CONTENT_MANIFEST". Any ideas? I am trying to serve static content for a remix application using module syntax for Workers

Sure thing <@453920106498621451> right now I am looking to deploy the same basic skeleton using both approached to compare them.

<@453920106498621451> Any ideas or resources that you might be able to point to that could help?

for Pages? <https://developers.cloudflare.com/pages/>

Workers Sites is deprecated and not actively maintained. Pages is the successor

Thank you for the response! Is `node_compat` supported in Pages?

Not really, we push more for our native Node.js support (<https://blog.cloudflare.com/workers-node-js-asynclocalstorage/>)

<@453920106498621451> 

I see, thank you for sharing that link!

If Worker sites are deprecated and the recommended way is to use Pages can you perhaps share an example of where we would run into a problem if we use Workers directly?

For example, (in the context of Workers) when using service worker syntax you can't really use durable object and would require module syntax. Is there such an example of where we would be blocked in using worker sites?

Skye had a look and also cant see why its failing, have logged a ticket: 2750090. Wrangler publish log is in the ticket

screen-shot-2023-03-31-at-01-42-29

screen-shot-2023-03-31-at-01-43-15

Sneak peek for an upcoming new library release

We just got banned from Cloudflare for egress from R2 and Workers. Would appreciate help in resolving this: https://twitter.com/_parasj/status/1641470460440481793

> Support confirmed this is a mistake but cannot fix it
Support escalated that case to engineering, who *can* fix it and will do so as soon as they can

I'll escalate the ticket up, R2 + video I'm guessing?

It's already been escalated through community and then to engineering, though if you can poke engineers that would work

There was one earlier this week that went out despite it

just pinged someone i know on the r2 team

This should be resolved now, really sorry for the disruption