That looks more like a Remix issue with how they're doing `createPagesFunctionHandler` to me 🤔
That looks more like a Remix issue with how they're doing 
createPagesFunctionHandler to me 
Ji was wondering if there is a way of having a function execute every so often?
JAlso another question is there a reason cloudflare doesn't use node?
Ihttps://developers.cloudflare.com/workers/learning/how-workers-works/
TLDR: V8 is the same engine as Chrome, and compared to Node.JS it has a highly optimized startup (around 5ms compared to 100ms+ for Node), is lighter weight, and isolates each customer's Workers from each other more effectively than Node can
TLDR: V8 is the same engine as Chrome, and compared to Node.JS it has a highly optimized startup (around 5ms compared to 100ms+ for Node), is lighter weight, and isolates each customer's Workers from each other more effectively than Node can
Jinteresting
RWhat do you mean? a bug?
My main issue is that I haven't found and 'official' example using Remix, CF Pages and functions (When you create a Remix project using CL Pages it doesn't create the functions folder).
But this seems odd to me because it's like this basic repo should show how to use functions within Pages
My main issue is that I haven't found and 'official' example using Remix, CF Pages and functions (When you create a Remix project using CL Pages it doesn't create the functions folder).
But this seems odd to me because it's like this basic repo should show how to use functions within Pages
HI think it is because you can’t really “use functions” with Remix. Remix uses functions for rendering, and the API, so if you write an API route in Remix, it will be compiled to Functions
HBasically, if you use a framework like that, don’t manually create your Functions. They might work, but they might bork everything…
RI don't understand. This example (without repo) it uses functions for authentication. I've tried it out, but I have the same error. But I guess it might work ... It's a bit confusing ...
https://dev.to/fllstck/serverless-remix-sessions-with-cloudflare-pages-4lpo
https://dev.to/fllstck/serverless-remix-sessions-with-cloudflare-pages-4lpo
DEV Community 👩💻👨💻
Using sessions with Remix is a pretty straightforward task. Usually, you put your session data into a...
HIt looks like what they are doing is having you mess around with the Remix Functions connector, which should be fine.
HEvery system that uses Functions for SSR requires a connector of some kind. Outside of that connector, you shouldn't be directly interacting with Functions.
Rok, I'll try to learn more in the Remix discord!! thx!
Wnot yet
WPros:
- Integrated with your project, so they get deployed at the same time
- Available on pages.dev
- They are just Workers anyway
- /shrug
BHello everyone, I am building a simple app to try pages/function/r2. When I test the app locally (running
wrangler pages dev --persist --r2=PIC -- npm run dev) everything seems to work with no errors, however when I deploy the app using cf pages UI of the app works with no errors but any attempt to trigger functions result in errors. On the client (i.e. in the console tab of the devtools section of the browser) I see internal server error 500, on the backend wrangler pages deployment tail I see Error: network connection lost. Initially I built the app using astro/vanillajs but then tried vite/react thinking that the error might be specific to astro, however the error persistsB
Bwhen I run
wrangler pages dev --persist --r2=PIC -- npm run dev to test locally the app is available on both port 5173(default for vite) and port8788(default for wrangler/workerd?). The one that is available on port 8788 works well while the one available on port 5173 results in same type of errors as the one on the prod (ie [project-name].pages.dev)BThank you. I am using
.then to handle the async part. I will try to replace with await but I feel that whole this error has something to do with deploy. It seems like requests I am making are not directed to functions and therefore return some weird errors
ZYou still have to return that fetch call, even if you use then.
Z(Either return it, or await it) but yeah, not related.
ZIs the repo public on GitHub?
BGitHub
Contribute to bkyerv/r2-demo development by creating an account on GitHub.
ZDoes the save-url function work?
Byes, that one returns url as expected (string value)
ZHmm, and it all works locally on :8788?
Bcorrect
Bthis is 4th day I am struggling to solve this issue
B
Bhere is the build confs
BI can confirm that build artefacts end up in the
dist folderZand you have the R2 bucket binding set up?
BYes, in the dashboard I declared variable PIC to my r2 namespace
KHow big is the file you’re uploading
B53kb
ZOK, so I got it working by doing this:
However: you probably want to stream the contents to r2 and this will buffer it in the worker, and I have no idea why it works locally.
Edit: Here's what you want:
However: you probably want to stream the contents to r2 and this will buffer it in the worker, and I have no idea why it works locally.
Edit: Here's what you want:
Bwhat is the difference/impact between buffer method and stream method?
ZThat gets a
readableStream from the uploaded File and passes it along, so you're not buffering the file contents.BThank you! Thank yoU!
Zthis must be a quirk of the differences between the local dev env and production. when pages gets support for
--experimental-local maybe your original code will stop working locally
JThis code is specific to my app, but you could do something similar.
I call
I call
getUsesMiddleware with a URL to decide if I need to do extra stuff with the request.ZContinuing the logs discussion from #workers-discussions … this morning as I was debugging, it seems like half the time I
wrangler pages published, the resulting deploy would never return any logs. Half the time it did. So i would connect, do some requests, and if no logs came through, I’d publish again and try again. Over about 10 deploys, it worked half the time.