does middleware count towards your functions quota?
does middleware count towards your functions quota?
functions/_middleware.ts for 'all requests, including in front of static files', can't tell if there's any granularity for static files_routes if you wanted: https://developers.cloudflare.com/pages/functions/routing/#create-a-_routesjson-filecurl, or anything that can make HTTP calls. They can be made to respect CORS, but by default do not
When using advanced mode, you need to bundle the worker—Cloudflare Pages build system doesn’t handle the bundling (if I recall correctly.)

Request type doesn't have a parsed body. This allows you to skip reading it if you don't actually need to parse it yourself. The await request.json() part tells it to begin pulling the body in, and parse it as JSONfunctions/hello.ts can be fetched like fetch('/hello') in my fullstack app? http://127.0.0.1:8787/hello but fetching it gives an error Invalid URL string. checkURLwrangler pages dev dist/. Same using wrangler pages functions build. This last says wrangler pages deploy dist/ --project-name my-project.11:31:45.603 Found Functions directory at /functions. Uploading.
11:31:46.776 ✘ [ERROR] 26 error(s) and 0 warning(s) when compiling Worker.
...
11:31:46.810 [[route]].ts:6:30: ERROR: Could not resolve "hono"
11:31:46.810 [[route]].ts:9:23: ERROR: Could not resolve "hono/cloudflare-pages"
11:31:46.810 [[route]].ts:10:21: ERROR: Could not resolve "hono/html"functions/_middleware.ts_routescurl //service worker
const body = JSON.stringify({
eventData: event.data,
shown: true,
})
fetch(`http://127.0.0.1:8788/cf/log-notification`, {
method: "POST",
"Content-Type": "application/json",
body: body,
}) // In CF function.
export async function onRequestPost(context) {
console.log(context)Requestawait request.json()// In Pages Function
export async function onRequestPost(context) {
console.log(await context.request.json());
// Do something else
}