what was odd for us and is still happening, after a deploy at 6pm, the worker has something to check the req pathname and then basically set that pathname in a cookie.
For some reason, the request for our main.js was being picked up in the worker as the req pathname and being set client side.
The actual worker code wasnt changed, but only the KV assets. Im guessing it couldnt find the main.js or something because the manifest in the worker didnt tie up to the hashed main.js
Something like that.
Is there no way to tell when a specific worker has caught up with deploys?
unfortunately we need specifically this algorithm for compatibility w/ a legacy client; we're aware of the security issues but don't have a choice here
PKIjs is a pure JavaScript library implementing the formats that are used in PKI applications (signing, encryption, certificate requests, OCSP and TSP requests/responses). It is built on WebCrypto (Web Cryptography API) and requires no plug-ins.
A library that generates OpenAPI (Swagger) docs from Zod schemas - GitHub - asteasolutions/zod-to-openapi: A library that generates OpenAPI (Swagger) docs from Zod schemas
Is there a way to get access to the cloudflare rendering api (puppeteer). I would like to switch away from browserless to cloudflare... anyone know how to get access? Already signed up for the waitinglist...
Workers Browser Rendering API is our out-of-the-box solution for simplifying developer workflows, including capturing images or screenshots, by running browser automation in Workers. If you’re interested, sign up for the waitlist.
Vitest would probably be best, as it supports hooking into the Vitest family of testing utilities, while unstable_devunstable_dev just allows you to run