wrangler, which you can add with a CLI flag(--node-compat). The other is a compatibility flag, which adds support for certain node packages directly through the runtime(nodejs_compat).wrangler deploy --dry-run --node-compat --outdir dist and then rename it to public/_worker.js. It just isn't very ergonomic./opt/build/cache/cwd/.cache
13:35:15.682 : EACCES: permission denied, mkdir '/opt/build/cache'/opt/build/cache/cwd/.cache
13:35:15.682 : EACCES: permission denied, mkdir '/opt/build/cache'wrangler pages deploy output--project-name and --branch which'll probably give you what you're loooking for?pages-action is a good solution too: https://github.com/cloudflare/pages-action
cloudflare/pages-action but I have been getting deployment failures for about 3 days now.request.cf 
x-vercel-? headers, e.g. x-vercel-ip-longitudenodewrangler deploy --dry-run --node-compat --outdir distpublic/_worker.jswrangler pages deploy output--project-name--branchpages-actioncloudflare/pages-actionCloudflare API returned non-200: 403
API returned: {"success":false,"errors":[{"code":10000,"message":"Authentication error"}]}
/home/runner/work/_actions/cloudflare/pages-action/v1/index.js:22082
throw new Error("Failed to get Pages project, API returned non-200");
^
Error: Failed to get Pages project, API returned non-200request.cfx-vercel-?x-vercel-ip-longitude