what url are you accessing, what is the logs saying/what is the strange errors? https://developers.cloudflare.com/workers/learning/logging-workers/

Can I simply add the cf-related package into my existing project?

so literally just // as the route then doing

return fetch(request)

and I was just logging the url which looked to be okay.

sorry, what's the issue/error then?

what framework is that?

next.js?

passing through to nextjs yes

what is the client error? CTRL + SHIFT + i (or F12) and then Console tab

TypeError: Failed to construct 'URL': Invalid URL

trying to build the worker as reverse proxy

the route is fine if I access next site directly

Why are my images not showing when I deploy to Cloudflare? My images are fine when I deploy to Vercel...

You should be good now 🙂

Hey there, are you using Next.js by any chance?

If you're using service calls in workers, does this effectively grant you multi-threading, or do they still end up running in the same thread/event loop? https://blog.cloudflare.com/introducing-worker-services/

Is there a good simple log aggregation tool that's good for workers... the over complexity of tools like NR and Splunk these days is just ... they're like the Atlassian of logging now. Anything out there with a free tier that just, you know, aggregates logs and maybe has a good interface?

Service bindings are same isolate/thread.

I occurs to me there might be a better channel for this question. Let me know if I should move it.

Thought so. Too bad 🙃

Yes, I'm using next.js

So, the

next/image

component uses a default Image Optimization API that Vercel is intercepting the requests for for you. However, this API is not included in edge runtime builds, and therefore you need to either use normal

img

elements or supply a custom loader to the

next/image

component using something like Cloudflare Image Resizing - https://developers.cloudflare.com/images/image-resizing/integration-with-frameworks (this is an area that we're looking at improving, but at the moment, those are your options)

Thanks. Atleast I know now. I've been scratching my head for hours with this. so custom loader you mean

const customLoader = ({ src, width, quality }) => {
  return `https://s3.amazonaws.com/demo/image/${src}?w=${width}&q=${quality || 75}

}

Yeah, something like that.

Thanks!

Another quick Q can I use lazy load from lazy loader package?

I've not tried that out personally so I'm not sure. Feel free to give it a go though - I'd be interested to hear how it goes 🙂

How do I not acknowledge a message in CF Queues? Should I just throw an error? Context: The producer starts a job and send the job id in the queue, the job usually takes 15s-20s to complete but so the the consumer time is set to check every 15s. Now the consumer should check if the job is completed, if so then do some operation (save to db) etc and the job id should get removed But if the job isn't completed then it the Id should stay in the queue for the next 15s to get picked by another worker.

Nevermind. There's a

ack

method on the

message

https://blog.cloudflare.com/messages-at-your-speed-with-concurrency-and-explicit-acknowledgement/

Hey guys, the command

wrangler secret:bulk

still exists?

ts
npx wrangler secret:bulk .\secrets.json --env jwt

X [ERROR] Unknown arguments: env, secret:bulk, .\secrets.json