Safari is the one I'll be hoping for - Safari on iOS is a big chunk of our users

sakuta•5/24/23, 7:22 PM

what permissions does my api token need for wrangler deploywrangler deploy? i'm using only Workers Scripts:EditWorkers Scripts:Edit permission at the moment and get an "unauthorized" error in my logs...

NNeiki i cant find anything to workers or crons in the notifications tab, only about pa...

Neiki•5/24/23, 7:26 PM

bump

Peter Belbin•5/24/23, 8:00 PM

hey there folks. question: https://github.com/cloudflare/wrangler-legacy/pull/2221 talks about being able to mark assets for future expiration of cached content to avoid users getting 404 errors when a new deployment happens for Wrangler workers. It also talks about providing something similar for 2.x (and now we're on 3.x). What's the story with this currently (particularly for 3.x). How does KV content get held over until the upgrade is done currently? Really want our users to not see 404 errors because they've been cuaght mid-update.

GitHub

fix: expire unused assets on site upload by caass · Pull Request #2...

backport of cloudflare/workers-sdk#587
currently, we just delete unused assets when uploading a new version
of a workers-sites project. this can cause problems when a user
accessing an old site get...

James•5/24/23, 8:05 PM

I believe in v2/v3 with Workers Sites, old assets are deleted as soon as new ones are published (ref: https://github.com/cloudflare/workers-sdk/blob/4082cfcbdf08740d4a608d3d87df22e51ad0ce4a/packages/wrangler/src/sites.ts#L319). The holistic solution these days would be to migrate to Cloudflare Pages (https://pages.cloudflare.com/) where development efforts are focused instead of Workers Sites

NNeiki bump

Cyb3r-Jak3•5/24/23, 8:10 PM

Workers doesn’t have error notifications. You have to put those in your script

CCyb3r-Jak3 Workers doesn’t have error notifications. You have to put those in your script

Neiki•5/24/23, 8:18 PM

but i cant catch the "Exceeded Resources" thing, it just happens sometimes i cant really say why its weird (only happend twice so far) but i thought maybe i can let me notify or something

kianOP•5/24/23, 8:25 PM

https://developers.cloudflare.com/workers/platform/tail-workers/ if you're on a paid plan

Tail Workers · Cloudflare Workers docs

A Tail Worker receives information about the execution of other Workers, such as HTTP statuses, data passed to console.log() or uncaught exceptions. …

Neiki•5/24/23, 8:26 PM

thanks and yes

NNeiki thanks and yes

Neiki•5/24/23, 8:48 PM

nvm sorry i found it, sorry for ping

Original message was deleted

dave•5/24/23, 9:11 PM

Correct. It's a bit annoying to have to have different preloading implementations for Chrome vs Safari though. For ease of use, we just stick with doing preloading client side for now.

Kkian Safari is the one I'll be hoping for - Safari on iOS is a big chunk of our users

dave•5/24/23, 9:12 PM

and those are the ones with the slow interwebz who you care about usually

dave•5/24/23, 9:17 PM

@sathoro btw Supabase staff will turn off rate limiting for your project if you ask them and say it's because you're using a Worker. Don't think you were running into issues yet, but figured I should share the info.

Nick Harris•5/24/23, 9:55 PM

Is it possible to use an HTTP proxy server when making outbound fetch calls from a Worker? I have some external services that are IP-restricted, and since CF Worker IPs aren't static I need to proxy it through another server (via tunneling) to make the call.

Nick Harris•5/24/23, 10:03 PM

Ah, gotcha, so you just made requests directly to the nginx reverse proxy?

Nick Harris•5/24/23, 10:04 PM

Thanks, seems like that'll end up being the lightest solution

Walshy•5/24/23, 10:29 PM

looks like you're using JavaScript not TypeScript

Walshy•5/24/23, 10:29 PM

if you remove the typing, it should work

Walshy•5/24/23, 10:42 PM

what's your full code?

Chaika•5/24/23, 10:54 PM

iirc you're missing node_compat? Or browser isn't set? I got that same error when I was setting this up yesterday, and it was fixed by me copying their wrangler.toml, can't remember if it was node_compat specifically or something else though. If you don't have it set at all though, you should

Chaika•5/24/23, 10:55 PM

your wrangler.toml should be like:

name = "browser-worker"
main = "src/index.ts"
compatibility_date = "2023-03-14"
node_compat = true
workers_dev = true

browser = { binding = "MYBROWSER", type = "browser" }

name = "browser-worker"
main = "src/index.ts"
compatibility_date = "2023-03-14"
node_compat = true
workers_dev = true

browser = { binding = "MYBROWSER", type = "browser" }

Make sure you're not trying to test locally as well. If you're on the latest wrangler/wrangler@3, use npx wrangler dev --remotenpx wrangler dev --remote

Walshy•5/24/23, 11:09 PM

yeah seems like MYBROWSER isn't defined as a browser binding

Walshy•5/24/23, 11:26 PM

aww man... you do need 3.0

Walshy•5/24/23, 11:27 PM

you can use unsafe for now

[[unsafe.bindings]]
binding = "MYBROWSER"
type = "browser"

[[unsafe.bindings]]
binding = "MYBROWSER"
type = "browser"

Neiki•5/25/23, 7:20 AM

i also have an error with tail workers: workers-and-pages-helpTail worker is not working

Safari is the one I'll be hoping for - Safari on iOS is a big chunk of our users

Similar Threads

Similar Threads

Similar Threads