Maybe I'm misunderstanding the documentation, but shouldn't

wrangler pages dev / --port 5000 --proxy 5500

run the server on port 5000 and serve the static pages located in the root folder on port 5500

The proxy command is for if you're fetching assets from a different dev server, it'll fetch them from that port

If you're just serving static assets, you should not specify the proxy argument

It’s my understanding that we can’t use CF Functions with NextJS — static or Edge Runtime. Is that correct?

Static as in exporting static files wouldn't have any dependency on Functions - as for Edge Runtime, take a look at

Ok, thanks!

is it possible to define a worker cron job alongside a set of functions?

or at least within a _worker.js file w/o functions?

Did I read somewhere correctly that function logs don't work yet on direct uploads?

They should be working fine now

Just need to make sure your wrangler version is relatively new

Ah will update! Does the wrangler version also influence whether logs are visible in the dash?

the issue was that older wrangler versions didn't correctly upload something to the api - so the functions tab of the deployment wouldn't know there were any functions

meaning it also can't show you the logs in the dash

however the wrangler command for tailing pages deployments should work regardless

Makes sense, thanks for the info. Will update! EDIT: It works, woohoo!

Maybe also try from the command line:

wrangler pages deployment tail
wrangler pages deployment tail https://....SOME_SPECIFIC_DEPLOYMENT_URL

Yes, this works for me now 🙂 I got confused initially because I tried to use it and it didn't work, but turns out the deploy was broken

When I configure a normal function/[[path]].ts

const handleRequest = createPagesFunctionHandler({
    build
  });
  
  export function onRequest(context) {
    return handleRequest(context);
  }

I'm getting this error

[pages:err] TypeError: Cannot convert undefined or null to object
    at Function.entries (<anonymous>)
    at Object.createRoutes2 [as createRoutes] (C:\Users\trials\remix-pages\node_modules\@remix-run\server-runtime\dist\routes.js:17:17)
    at createRequestHandler$1 (C:\Users\trials\remix-pages\node_modules\@remix-run\server-runtime\dist\server.js:27:25)
    at createRequestHandler (C:\Users\trials\remix-pages\node_modules\@remix-run\cloudflare-pages\dist\esm\worker.js:26:23)

Any ideas? thx

That looks more like a Remix issue with how they're doing

createPagesFunctionHandler

to me 🤔

i was wondering if there is a way of having a function execute every so often?

Also another question is there a reason cloudflare doesn't use node?

https://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

interesting

I don't know why but service bindings in Cloudflare Pages Functions aren't working, the bindings are returning an empty object. are there issues in Cloudflare Pages Functions Service Bindings?

What 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

I 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

Basically, if you use a framework like that, don’t manually create your Functions. They might work, but they might bork everything…

I 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

It looks like what they are doing is having you mess around with the Remix Functions connector, which should be fine.