Hi I have a question, I'm using vite with functions, to run localy using wrangler pages dev command,
Hi I have a question, I'm using vite with functions, to run localy using wrangler pages dev command, is always run the vite build first?
RDATASTAR looks interesting, a small framework.. i am sure it can be run in a function itself, --- but isn't it a client side framework , not server side rendering.
Ryou need to build first, then run npx wrangler pages dev ./dist (output folder)
AHey guys, is there a way to use wrangler's unstable_dev with functions?
AI'm trying to create a Gatsby plugin that proxies functions to make them available for local development
AIf possible I'd like to avoid running wrangler using
child_process
NDoes anybody know what the expected behaviour is for active clients of a pages site after a deploy? Do clients continue to have their requests routed to the existing worker version somehow or does all traffic get re-routed immediately? I can't find this documented anywhere so I'm assuming its the latter but hoping to get confirmation.
ILatter. All future requests immediately hit the new version. If you want some sort of skew protection (similar to https://vercel.com/blog/version-skew-protection but not Vercel-specific) then you'll need to use a framework that provides that built-in.
N@Isaac McFadyen thanks for the quick response. So to accomplish this you'd need a way for the client to direct requests to the specific function version it was served against? Is there a way inside the function to get the details of the current function(i.e. version or url)?
IYou'll need to use a framework-specific implementation for versioning. For example, SvelteKit has https://svelte.dev/docs/kit/configuration#version
N@Isaac McFadyen Thanks for the example. If I'm not mistaken thats not quite the same as the Vercel link. SvelteKit just seem to be using the version to decide whether they should reload the app or not. By contrast Vercel seem to be tracking the function version that the app is served from so that any subsequent requests can be made in a way that they get routed to the same function. Even if this can be handled at a framework level, I would expect that within the pages function that serves the app initially, you would need to access the id of the function(and consequently the preview url) so that you had a way to force the routing of subsequent requests.
ISo yeah, when I linked to Vercel's link I just meant that that's the kind of feature you're looking for. But you'll likely need to do a full reload—I don't believe (although I might be wrong) that assets from a past deployment will be available on Pages once you've pushed a new version, so you'll likely need to reload the page.
Nyeah, I think as long as you had the preview url for the current deployment you could work around that by using the preview url as your base url for everything after the initial load(although you might not want to expose that url). With that said, look's like you need the version metadata api to get the deployment id which is not currently available in pages functions by the looks. Thanks for your help.
BBit of a beginner's question, but how do I use pages plugins? My site is static, so no node or wrangler or anything. I have a script that runs in the build, but currently no workers or functions. If I add
functions/_middleware.ts
JUncaught SyntaxError: Identifier '__cf_cjs' has already been declaredDo workers not support Mongodb driver as its based on v8.. The docs say to use Realm-Web (sdk) but it looks like a dated article, as i hear that library is now deprecated.. its been a few months, could cf update the doc to reflect that mongodb drivers are no longer support natively? (https://blog.cloudflare.com/workers-adds-support-for-two-modern-data-platforms-mongodb-atlas-and-prisma/)
IIn general (sadly) CF doesn't usually update past blog posts.
Rsad, confuses a lot of customers thinking it does, and then building... and then ohh that was an old outdated post...
RHono with pages workers : I created a functions/api/test.js as follows:
when i try to go to /api/test the function is not picked up. I have created other routes that do work using the function systam, but with hono its a 404, what could i be dong wrong.
import { Hono } from 'hono'
const app = new Hono()
app.get('/', (c) => c.text('Hello Cloudflare Workers!'))
export default appwhen i try to go to /api/test the function is not picked up. I have created other routes that do work using the function systam, but with hono its a 404, what could i be dong wrong.
IMongoDB Realm is officially deprecated so theoretically anyone trying to use the SDK in the first place should run into many warnings (including on the MongoDB page itself) before even trying to deploy to Workers.
RHey, how do i add secrets for pages functions? should they be in the Variables and Secrets or in .dev.vars ? i build the app in ci/cd not in cloudflare
Wdashboard
Wor through
wrangler pages secret putRThanks, also the wrangler is kind of messy cause for worker you get the list as json and for pages you get them as a text 
ZWhat changes did you make yesterday that caused our webpage to fail to compile?
Wno release yesterday, can you expand?
Pcan i use a node js server to test cf functions locally, or is the syntax wildly different? (hint: i don't know either well enough yet)
wrangler and miniflare don't seem to work on my platform, keep throwing errors when installing
wrangler and miniflare don't seem to work on my platform, keep throwing errors when installing
TYou can always just spin up a private test repo and create a random pages.dev site and test your functions routing and deployment there and remove it afterwards :shrugs:
Pi mean... you aren't wrong, i will do that. well i am basically already doing that, it just.. sort of feels bad when i push it and see that there's a build time error because i forgot to close a (
but yeah, this is the fastest, they also have a log for functions in the dashboard itself. cloudflare also has a workers playground apparently but I don't know how to make it work for functions so
yeah, fastest way is making a random page
but yeah, this is the fastest, they also have a log for functions in the dashboard itself. cloudflare also has a workers playground apparently but I don't know how to make it work for functions so
yeah, fastest way is making a random page
TThere are real time logs in the functions dashboard tab for your latest build.
You can also build more advanced logging into your functions so that your logging to the realtime functions is more verbose. I think, if you ever got wrangler working, you can log functions to that tool as well, its not just for workers.
You can also build more advanced logging into your functions so that your logging to the realtime functions is more verbose. I think, if you ever got wrangler working, you can log functions to that tool as well, its not just for workers.
Pit's really odd how cloudflare seems like a full blown host sometimes but other times it seems pre alpha stage
MI have a question about nodejs compatibility -- hope this is the right place to ask -- I'm trying to run metaplex (https://www.npmjs.com/package/@metaplex-foundation/js) on cloudflare pages functions, but the build fails because of missing nodejs apis, which to my understanding should be available because I'm using nodejs_compat... Any ideas how to resolve this, or approach this problem differently? Thanks
MFWIW I resolved it by upping the compat date and changing nodejs_compat to nodejs_compat_v2 , which I was under the impression should enable the same things, but I guess they do not 
Wthere's a bug where it doesn't - fix coming soon
MI'm struggling to use a page function (for a simple contact form) with Astro. I've put code in functions/contact.js but it fails to recognise the function when deployed with Pages.
XI am trying to deploy the Remix application to Cloudflare pages. Here is the structure and the error that I get when i run
npm run start after successfully running npm run build
XHere is the
/functions/[[path]].ts file TIs there a general guide on how to view live function logs for your deployed cloudflare pages site with wrangler?
TIve done some searching and cant find much that explains the process?
Jhttps://developers.cloudflare.com/workers/wrangler/commands/#deployment-tail
wrangler pages deployment tailis probably what you're looking for
FHello everyone, I have a small question. I'm using Cheerio on Workers, I wanted to know if I could use it in the same way in Functions? And how I could include it in Functions. Thank you in advance for help.
AHello everyone, I am a starter of Cloudflare and I am building a remix app with Cloudflare pages. I have a trouble matter now, so when I try 'wrangler pages dev', it's failed with error,
✘ [ERROR] "await" can only be used inside an "async" function
✘ [ERROR] "await" can only be used inside an "async" function
�Could you share a snippet where you encountering the issue?
THi guys, I’m trying to set up my site with Cloudflare Pages and Functions. First, I followed this guide - https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/get-started/
- and succeeded to run locally. Then, I wanted to create a simple API served by a Worker, so I followed this guide - https://developers.cloudflare.com/pages/functions/get-started/ . But for some reason, my
functionsfolder always got ignored. I tried putting it at same level as
, underpackage.json
, undersrcsrc/app, nothing worked. The build output (.vercel/output/) doesn’t contain my function. When I run the website locally and try to call my APIlocalhost:8788/api/helloworld, I only see 404 Error. Do I need to declare anything inwrangler.tomlor change my build command (currently it is like in the first guide) for myfunctionsfolder to work? Thanks in advance!
Cloudflare Docs
Deploy a full-stack Next.js app to Cloudflare Pages
Cloudflare Docs
This guide will instruct you on creating and deploying a Pages Function.
DIf your nextjs app is static, you can use cloudflare pages'
But for SSR, you need to use nextjs API routing with adapters like
functions directory api routing.But for SSR, you need to use nextjs API routing with adapters like
opennext-cloudflare for cloudflare workers assets and next-on-pages for cloudflare pagesDCloudflare Pages (Next.js SSR): https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/get-started/
Cloudflare Workers + Assets (Next.js SSR): https://developers.cloudflare.com/workers/frameworks/framework-guides/nextjs/
Cloudflare Workers + Assets (Next.js SSR): https://developers.cloudflare.com/workers/frameworks/framework-guides/nextjs/
Cloudflare Docs
Deploy a full-stack Next.js app to Cloudflare Pages
Cloudflare Docs
Create an Next.js application and deploy it to Cloudflare Workers with Workers Assets.
CI'm coming from python and routers will generate the OpenAPI
Next.js has a way to do that too, but I'm not using next.js rather just regular CloudFlare pages functions native
Anyone know how to make the _middleware catch a route and generate the OpenAPI spec live?
A better question that may lead me to the answer - anyone know exactly which router functions was based on, so I can adapt some other middleware in that ecosystem, or is this an entire new router and no existing middleware ecosystem exists to leverage?
Next.js has a way to do that too, but I'm not using next.js rather just regular CloudFlare pages functions native
Anyone know how to make the _middleware catch a route and generate the OpenAPI spec live?
A better question that may lead me to the answer - anyone know exactly which router functions was based on, so I can adapt some other middleware in that ecosystem, or is this an entire new router and no existing middleware ecosystem exists to leverage?
�Hello! I have been trying to make a simple authentication system using pages functions (I'm using JavaScript) and in the build log it is saying this:
now in my repo, I have set up the functions as following:
So is there something I can do to fix that error?
now in my repo, I have set up the functions as following:
So is there something I can do to fix that error?