Im trying to make an admin page for modifying settings stored in kv and since functions are now generally available I thought why not take advantage of that

@User yes the worker is in the functions folder. I only get the 404 page from my hugo site when I try to go to the functions path

are you sure it's a 404 and not an error with the worker. I saw in the forum you said you where using workers before. You have to code workers for pages slightly different than normal workers

is it possible to have two patterns like

/functions/[foo]/[bar].ts

? i keep getting 404 and i'm not sure if it's my fault or not

"In turn, the URL segment(s) that match the placeholder will be available under the context.params object using the filename placeholder as the key." in docs implies yes, but it ain't working

Not presently. You'll have to do

/functions/[[captureAll]].ts

and parse out individual segments yourself unfortunately.

I've got a note to myself to look into adding support for multiple parameters like this, but haven't gotten around to it yet.

if you're on that,

functions/blah-[x].ts

would also be great. basically, steal SvelteKit routing 😉

(this really should exist as a library...)

Has anyone seen this error before? I'm trying to get functions working locally with create-react-app.

TypeError: Web Socket request did not return status 101 Switching Protocols response with Web Socket
    at Server.<anonymous> (file:///C:/Users/mike/github/menu/front/node_modules/@miniflare/http-server/dist/src/index.js:553:22)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

I have seen it before, but I can't remember exactly how I solved it.. can you list the exact command that you use to start running things locally?

Sorry, WebSockets aren't supported right now, so you've got to do this little hack at the moment.

This is the command I'm using to run things:

npx wrangler pages dev -- craco start

Thanks for the quick reply @User & @User!

I've updated things, and that fixed the error! But browsing to

/api/test

doesn't work :/

it should invoke /functions/api/test.js, but it looks like react router is snagging this request instead of letting cf handle things

That greatly depends on how you configure your react-router yes.. very possible

Problem is that they have like 3 versions of react-router and I have only really used v4, so I am not entirely sure how you would solve it

How are you requesting

/api/test

?

oh gotcha, that makes sense. I'm using

"react-router-dom": "^5.3.0"

and they seem to be using

"react-router-dom": "^6.0.1"

in their example: https://github.com/cloudflare/images.pages.dev I'm not sure if the version would make that big of a difference Does react-router have a config file for this somewhere?

I'm just opening it in chrome. Everything works fine when I push things to CF, but it's not playing nicely in my local environment

/functions/api/test.js

export const onRequest = () => {
  return new Response(new Date().toISOString())
}

Sorry, I meant, what’s the client-side code that’s calling that?

there isn't any client-side code calling it right now, I'm just trying to get the test working, and then I'll start building out the frontend and backend 🙂

Ah, okay. I wouldn’t worry about React Router intercepting the request then. Any `fetch`es or whatever that you make should go straight to that endpoint.

Quick question regarding pages-functions pricing. I am planning on adding a rather small feature in a function and would like to use it at example.com/my_function, every other url should be default pages behaviour. Is every request against example.com counted as a function call that falls back to default resource serving or are only calls to /my_function billed?

In this beta, yes. We're hopeful that we'll be able to be smarter about that before we GA and start charging.

(Yes to "every request against example.com counted as a function call")

Ok thanks, that's how I understood the current documentation and wondered if this is really the case. At least for me that would be blocker to enable pages-functions to prod and would keep my workers split from pages.