sad, confuses a lot of customers thinking it does, and then building... and then ohh that was an old
sad, 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
is probably what you're looking forwrangler pages deployment tail
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 in
or change my build command (currently it is like in the first guide) for mywrangler.tomlfunctionsfolder 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-pagesCloudflare 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?
�Nevermind my it was the structure of my files that was broken lol
I
JQuestions:
Under the routing information in the docs, wasn't made explicit either regarding utility and helper funcs.
For EX: I have repeating code in multiple routes that are exporting onRequest that i would like to refactor out to to a single util module in the same directory, and not deploy that module as a route
- How does cloudflare functions handle utility/helper .ts or .js functions in the functions directory when using file based routing?
- Any way to see what our actual functions bundled build file that is going to be deployed will look like while developing? npx wrangler pages ... something
Under the routing information in the docs, wasn't made explicit either regarding utility and helper funcs.
For EX: I have repeating code in multiple routes that are exporting onRequest that i would like to refactor out to to a single util module in the same directory, and not deploy that module as a route
�Answers to your first question: it will handle it as actual functions resulting in the
Of course for example, and for the second question I do not believe you can see the bundled up functions build file.
No routes detected when building functions directory as these helper functions do not follow the functions format, you should just create a src folder in the output directory and have all your helper functions there, you can access them from your pages functions as follows:import { sendEmail } from "/src/utils/email.js";Of course for example, and for the second question I do not believe you can see the bundled up functions build file.
�Nvm in this case (I didn't read the whole message at first), it will treat this as a functions file still.
JHmm interesting!
So I have refactored my code and created two utility modules inside of the /functions directory:
I have also tested if there was any routes deployed in dev mode using npx wrangler pages dev out/ for the utility modules in /functions & am getting 404 errors for both but I'm not sure if this will replicate to prod
I did a search in this discord regarding 'utility functions' and seem to have found one screenshot discussing a similar problem, but I couldn't find any solid citations in the docs so I thought to double check here
So in general, is the correct way to handle utilities and helper methods in the /functions dir to define them outside of the /functions dir and import them in?
Or do we just trust that wrangler will appropriately deal with any code in the /functions dir that doesn't export onRequest?
So I have refactored my code and created two utility modules inside of the /functions directory:
- One for mailing functionality
- One for google oauth token fetching
I have also tested if there was any routes deployed in dev mode using npx wrangler pages dev out/ for the utility modules in /functions & am getting 404 errors for both but I'm not sure if this will replicate to prod
I did a search in this discord regarding 'utility functions' and seem to have found one screenshot discussing a similar problem, but I couldn't find any solid citations in the docs so I thought to double check here
So in general, is the correct way to handle utilities and helper methods in the /functions dir to define them outside of the /functions dir and import them in?
Or do we just trust that wrangler will appropriately deal with any code in the /functions dir that doesn't export onRequest?
�Hello, sorry for the late reply, and yes the correct way to handle them is, infact putting them outside of the functions directory, but be sure not to put them in the root directory or put them in a root directory folder, they are not accessible for you on build, you should do what I said. Move those utility functions to a src folder in your output directory and access it using
Furthermore apparently what they state in the first picture is the helper functions will not be bundled unless there is a functions file that imports it.
"/src/theRestOfThePathToYourFile";Furthermore apparently what they state in the first picture is the helper functions will not be bundled unless there is a functions file that imports it.
JUnderstood, thank you so much for the help!
Do functions inside the /functions directory have access to files deployed in the static bundle in cf pages?
Couldn't find any documentation regarding this when i tried looking sadly
I am also using typescript --
so defining utility .ts files in my /output deploy directory and compiling them using /output/src/tsconfig.json is possible but not desirable
I guess I can also use different import paths from .ts and .js but thats also not desirable either lol
I guess I can just duplicate code and copy paste in all my api endpoints if cloudflare functions really doesn't support helper/util functions in a straightforward fashion which is honestly very tough lol
Do functions inside the /functions directory have access to files deployed in the static bundle in cf pages?
Couldn't find any documentation regarding this when i tried looking sadly
I am also using typescript --
so defining utility .ts files in my /output deploy directory and compiling them using /output/src/tsconfig.json is possible but not desirable
I guess I can also use different import paths from .ts and .js but thats also not desirable either lol
I guess I can just duplicate code and copy paste in all my api endpoints if cloudflare functions really doesn't support helper/util functions in a straightforward fashion which is honestly very tough lol
�Okay so I just tested and no they don't even support external access, not even to the output directory... sorry for the misinformation, but yeah you aren't gonna be able to define helper functions.
�I mixed up server side rendering images from the build directory and being able to access it from the function, you actually can access that directory if you are using html (like if you are using ssr) but you can't really use any helper functions defined there.
JNo worries! I appreciate the input regardless.
This really isn't great if that is the case!
I also combed through github repos since I'm sure I'm not the only one that has wanted to have utility modules and found stuff like:
1) https://github.com/Charca/cloudflare-pages-auth
User has defined utils.ts in /functions and has exported the functionality into api endpoints
2) https://github.com/whyun-pages/docker-registry
From cloudflare functions docs: "Writing your Functions files in the /functions directory will automatically generate a Worker with custom functionality at predesignated routes."
From another users question here (https://community.cloudflare.com/t/cloudflare-pages-functions-bundled-or-not/577646): "They are indeed all bundled into a single Worker."
Not clear how this is going to treat functions/modules that are straight helper code and that don't define any onRequest handler -- are those two repos above dealing with utility methods/helpers incorrectly?
This really isn't great if that is the case!
I also combed through github repos since I'm sure I'm not the only one that has wanted to have utility modules and found stuff like:
1) https://github.com/Charca/cloudflare-pages-auth
User has defined utils.ts in /functions and has exported the functionality into api endpoints
2) https://github.com/whyun-pages/docker-registry
- Another repo that has defined a util file in /functions and exports functionality to use in onRequest endpoints
- I guess what really even happens to the /functions dir when you say something like "npx wrangler pages publish out/"?
From cloudflare functions docs: "Writing your Functions files in the /functions directory will automatically generate a Worker with custom functionality at predesignated routes."
From another users question here (https://community.cloudflare.com/t/cloudflare-pages-functions-bundled-or-not/577646): "They are indeed all bundled into a single Worker."
Not clear how this is going to treat functions/modules that are straight helper code and that don't define any onRequest handler -- are those two repos above dealing with utility methods/helpers incorrectly?
JAlso Unknown can you try defining a utility javascript file in the /functions directory and seeing if on prod it is treated as a proper route?
I also couldn't find how to see all deployed /functions routes on the cloudflare dashboard for a domain but i think that would be helpful here
I also couldn't find how to see all deployed /functions routes on the cloudflare dashboard for a domain but i think that would be helpful here
JI think this screenshot may be relevant but we'll see
�I just tested, they are treated like relative file paths, I only tested with a simple
export function log() { console.log('So How Is Your Day?'); and it works so far.�I imported the function using this:
import { log } from "./sendLog.js";�(Both files are in the same directory)
�I'll test with an onRequest now
�But I'm not sure how I'm gonna test an onRequest exactly...
�Nvm
