And this works with the Pages CI too, using the filesystem routing?
And this works with the Pages CI too, using the filesystem routing?
HYup, as long as you configure Pages to clone the right directory(so that the external import isn’t cut out), then it should build like normal
CWhat do you mean by the right directory? The root directory?
CAnd if I have a file at
functions/utils.ts, will that automatically become a route too, or does it need a onRequestonRequestGet/Post/etc to become a route (which becomes listed in _routes.jsonYes, as long as your root directory contains all of the code you import.
HIt will not. Routes are only generated when an
onRequest* export is presentCPerfect, thank you very much!
SHey all, been having some trouble trying to get up R2 + worker + image resize. The images are in the R2 bucket and are accessible through an existing worker (worker1). Another worker has been created with a route configured to /images/*.
Took the code from this https://developers.cloudflare.com/images/image-resizing/resize-with-workers/#an-example-worker and deployed the worker. When I try to access the worker (ie: example.com/images?image=https://worker1.com/cat.png), I'm hit with this
Took the code from this https://developers.cloudflare.com/images/image-resizing/resize-with-workers/#an-example-worker and deployed the worker. When I try to access the worker (ie: example.com/images?image=https://worker1.com/cat.png), I'm hit with this
Using Image Resizing with Workers gives you powerful programmatic control over every image request.
SAny suggestions on what I'm probably doing wrong here?
BHey functions team, I'm trying to deploy a simple hello world function. I am using nuxt.js and juxt content. I run it locally, no problem:
However, when I perform my deploy and then navigate to the page on the service, (it deploys and builds fine) but I just get a 404 .
it's the 404 provided by the framework (
npx wrangler pages dev -- npm run dev http://127.0.0.1:8788/helloworld = "Hello World"However, when I perform my deploy and then navigate to the page on the service, (it deploys and builds fine) but I just get a 404 .
it's the 404 provided by the framework (
nuxt.js) and i don't know how to override this / configure it to point to the pages function.BGitHub
I would really like some clarity regarding the following: (Edit: Forgot to add that I intended to ask @luc122c about this - thanks for any input!) I am a bit confused by this issue: Is the intended...
CHow does Cloudflare Pages Functions behave when importing files in the rest of the project (under the root directory, but not
functions) which import npm packages? (e.g. functions/index.ts -> src/schema.ts -> zodShould work fine
BThanks for this guidance, but how do I move my functions to nuxt's server endpoint? Is this inside of the
/serverdirectory? I've spent hours pouring over docs and I can't figure out how to do it. I'd be happy to write / contribute a documentation snippet or just include it in that github for others, I just don't know what to do.BI don't understand enough about the expectations of cloudflare functions to do any of that work confidently. It's not covered in the CF pages documentation and kind of goes against what's in the getting started guide. It feels like a hack but I just don't know enough about the systems to spend time on it. I think functions probably aren't for me.
B
will give this a try!BThanks
EIs there are an equivalent to
google-auth-library that will work in a function?
Aso i tried not using a functions folder completely, and just having /server/api/hello.ts that just returns 'hello'. in nuxt.config.ts i set
but it still doesn't work. do you happen to know if i am missing something?
but it still doesn't work. do you happen to know if i am missing something?
Aah it's because i'm using nuxt generate, which is for SSG sites, and that means i can't use the /server stuff at all
SI am using middleware in
I have replicated the issue in a minimal repo here – https://github.com/Shivam010/cloudflare-double-slashes-issue
I have also asked help on wrangler-sdk repo https://github.com/cloudflare/workers-sdk/issues/3677 but it feels like they are overburdened with other issues.
Am I missing something here? or is this an actual issue?
/functions//, wrangler doesn't run the middleware for the url.I have replicated the issue in a minimal repo here – https://github.com/Shivam010/cloudflare-double-slashes-issue
I have also asked help on wrangler-sdk repo https://github.com/cloudflare/workers-sdk/issues/3677 but it feels like they are overburdened with other issues.
Am I missing something here? or is this an actual issue?
GitHub
Contribute to Shivam010/cloudflare-double-slashes-issue development by creating an account on GitHub.
GitHub
Which Cloudflare product(s) does this pertain to? Pages What version(s) of the tool(s) are you using? latest What version of Node are you using? 20.1.0 What operating system are you using? Mac Desc...
SMore description on the issue
It's replicated in https://github.com/Shivam010/cloudflare-double-slashes-issue
There's a middleware in
And the
The issue is...
The middleware is properly invoked on
Links
Github Repo: https://github.com/Shivam010/cloudflare-double-slashes-issue
Hosted on: https://double-slashes-issue.pages.dev
It's replicated in https://github.com/Shivam010/cloudflare-double-slashes-issue
There's a middleware in
/functions/secure directory to be applied on all routes of /secure.And the
/out/secure directory contains a file one.html which should be served at /secure/one (but first the middleware needs to be invoked)The issue is...
The middleware is properly invoked on
/secure/one route but not on the //secure/one, whenever someone uses a double slash before the middleware directory, wrangler doesn't run the middleware and instead directly serve the pages.Links
Github Repo: https://github.com/Shivam010/cloudflare-double-slashes-issue
Hosted on: https://double-slashes-issue.pages.dev
/secure/one route – https://double-slashes-issue.pages.dev/secure/one//secure/one route – https://double-slashes-issue.pages.dev//secure/one/secure/one?allow route – https://double-slashes-issue.pages.dev/secure/one?allow (that's actually allowed by middleware)GitHub
Contribute to Shivam010/cloudflare-double-slashes-issue development by creating an account on GitHub.
SAnyway I can make a blog using pages functions and workers for my pages website?
DLook in the dashboard, in your pages project in the settings tab there is an environment variable option that you can set and encrypt for both preview and production branches
CCurrently trying to test Functions locally using
npx wrangler pages dev . (. contains a directory with functions) and getting the following error:
JTry downgrading to wrangler 3.4.0. 3.5.0 has an issue that's hiding some useful error logs from workerd.
Cworkerd/util/symbolizer.c++:99: warning: Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, use --test_env=LLVM_SYMBOLIZER=<path>.CI have LLVM 15.0.7 installed, and
llvm-symbolizer is in $PATH.Jany other errors? What's your functions look like?
CLLVM_SYMBOLIZER=(which llvm-symbolizer) npx wrangler@3.4 pages dev . seems to work!JIs there another line perhaps under that one? Can you screenshot again?
J...that really should not be required 
C
Jahh okay,
address already in useJyou have another
workerd