^ I didn't know if Zod was Workers-compatible or not but it sounds like it is, and yeah, Zod is IMO
^ I didn't know if Zod was Workers-compatible or not but it sounds like it is, and yeah, Zod is IMO the best
npm i @cfworker/json-schema. There are 31 other projects in the npm registry using @cfworker/json-schema.
preview or production (the only environments accepted by wrangler for a pages project), but I don't know how to intercept this at build-time with the Github Integration of a SolidStart app, build with Vite.preview app needs to make some API request from the client to an endpoint different form the production, and since Environment Bindings are only exposed from the context object of the workers I can't reference the correct URI for different remote environmentspreview is gonna be my staging while production is of course the prod.env.IMAGES.info(stream) call consume the ReadableStream and then env.IMAGES.input(stream) try to reuse the stream that is already consumed? Is there some magic going on there?env.IMAGES.info(stream) on a stream just to verify info and then pipe the same already-consumed (?) stream to R2 without any transformations? Or do I need to tee the stream?.info(stream) free? Do I assume that each call to <some transformations>.output() triggers one "unique transformation" quota usage? E.g. 5k free .output() calls per month then $0.5 per 1k thereafter?
workers.dev, which has Cache disabledfetch's..draw() commands that can be done in a single request? Through the existing draw: [] method, I have been limited to ~70 layers due to 16KB header limit, hoping this will be able to get around that but not sure if the binding is just doing a fetch() underneathWrangler did not find routes when building functions.
.draw()draw: []01:51:31.039 Cloning repository...
01:51:31.945 From https://github.com/chrismuntean/Event-Photography
01:51:31.945 * branch 471052acb01bd770cf02209e0756104342d22953 -> FETCH_HEAD
01:51:31.945
01:51:31.979 HEAD is now at 471052a Created backup file of original development worker
01:51:31.980
01:51:32.053
01:51:32.053 Using v2 root directory strategy
01:51:32.073 Success: Finished cloning repository files
01:51:33.605 Checking for configuration in a Wrangler configuration file (BETA)
01:51:33.606
01:51:34.708 No wrangler.toml file found. Continuing.
01:51:34.708 No build command specified. Skipping build step.
01:51:34.708 Found Functions directory at /functions. Uploading.
01:51:34.714 ⛅️ wrangler 3.101.0
01:51:34.714 -------------------
01:51:35.547
01:51:35.639 ✘ [ERROR] No routes found when building Functions directory: /opt/buildhome/repo/functions
01:51:35.640
01:51:35.640
01:51:35.733 🪵 Logs were written to "/root/.config/.wrangler/logs/wrangler-2025-02-25_08-51-35_301.log"
01:51:35.743 Warning: Wrangler did not find routes when building functions. Skipping.
01:51:35.744 Validating asset output directory
01:51:38.199 Deploying your site to Cloudflare's global network...
01:51:41.797 Uploading... (29/29)
01:51:41.798 ✨ Success! Uploaded 0 files (29 already uploaded) (0.28 sec)
01:51:41.798
01:51:42.005 ✨ Upload complete!
01:51:44.613 Success: Assets published!
01:51:46.372 Success: Your site was deployed!addEventListener('fetch', event => {
event.respondWith(handleRequest(event.request, event))
})
async function handleRequest(request, env) {
if (request.method !== 'POST') {
return new Response("Method Not Allowed", { status: 405 });
}
try {
...