Correct, it wont invoke the function for GETs if you do that
Correct, it wont invoke the function for GETs if you do that
wrangler pages deploy to deploy static files and Pages Functions. I would like to deploy only the Pages Functions, without deploying the static files. I.e. I'm using wrangler pages deploy ./build-output ..., which deploys the static files from ./build-output and also deploys ./functions by the file-based routing convention.wrangler pages deploy to deploy only the pages functions? If I have an empty directory with only the functions directory, would wrangler pages deploy know to upload the functions but not delete the static files already uploaded?
JSON.parse(await event.request.text());, but yeah it should always be in requestcontext object with env attached: https://developers.cloudflare.com/pages/platform/functions/api-reference/#types

wrangler pages deployment tail [deploymentId/url]No functions. Shimming...npm i <package> and import { foo } from "package" in your Functions files.c:\users\[user]\ , just needed to cd to \github\[repo]\ and run it from there12:43:50.447 ✘ [ERROR] Could not resolve "stripe"
12:43:50.447
12:43:50.447 checkout.js:4:19:
12:43:50.447 4 │ import Stripe from 'stripe';
12:43:50.448 ╵ ~~~~~~~~
12:43:50.448
12:43:50.448 You can mark the path "stripe" as external to exclude it from the bundle, which will remove this error.
12:43:50.448
12:43:50.448
12:43:50.450 ✘ [ERROR] Build failed with 1 error:
12:43:50.451
12:43:50.451 checkout.js:4:19: ERROR: Could not resolve "stripe"wrangler pages deploy ./build-output ..../build-output./functionsJSON.parse(await event.request.text());export async function POST(event) {
const db = event.platform?.env?.DB;`
}wrangler pages deployment tail [deploymentId/url]No functions. Shimming...npm i <package>import { foo } from "package"/project
/node_modules
/package1
/package2
/etc
/functions
/index.js # import { foo } from "package1"; here
/static
/index.htmlc:\users\[user]\\github\[repo]\