zsmooth
zsmooth
CDCloudflare Developers
Created by zsmooth on 2/6/2025 in #wrangler
i'm trying to `wrangler d1 migrations
this is all i see before it dies with WRANGLER_LOG=debug:
⛅️ wrangler 3.107.3
--------------------

-- START CF API REQUEST: GET https://api.cloudflare.com/client/v4/memberships?page=1
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
INIT: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
-- END CF API REQUEST
-- START CF API RESPONSE: OK 200
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
RESPONSE: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
-- END CF API RESPONSE
Saving to cache: {"account":{"id":"xxxxx","name":"xxxxx"}}
⛅️ wrangler 3.107.3
--------------------

-- START CF API REQUEST: GET https://api.cloudflare.com/client/v4/memberships?page=1
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
INIT: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
-- END CF API REQUEST
-- START CF API RESPONSE: OK 200
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
RESPONSE: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
-- END CF API RESPONSE
Saving to cache: {"account":{"id":"xxxxx","name":"xxxxx"}}
1 replies
CDCloudflare Developers
Created by svend on 1/10/2025 in #workers-help
Workers with static assets - asset caching?
I'll probably end up forcing assets through the worker so I can add the headers myself, but it bums me out 🙂
14 replies
CDCloudflare Developers
Created by svend on 1/10/2025 in #workers-help
Workers with static assets - asset caching?
yeah, this is a bummer. i understand why workers isn't automatically telling browsers to cache forever, but i really wish they'd port the _headers over from pages so we can do it ourselves when we know it's safe
14 replies
CDCloudflare Developers
Created by zsmooth on 1/28/2025 in #wrangler
wrangler feature request: i keep pushing
yeah - that's the same thing I do. it just adds friction every time i deploy a feature that needs a new secret cause i never remember to push it out first 🙂
4 replies