Not yet, but

https://github.com/cloudflare/wrangler2/issues/92 you're on windows?

Can we expect Pages Functions to go out of beta soon?

How easy it is to increase the current limit of 100,000 requests? And how much can we increase it?

Hey, there is a form in the pins to get it increased 👍🏼

I’d like to think around 3-4 months but CF don’t release public timelines

Thanks for the informations!

Has anyone had any success using a

_headers

file? I tried putting it in the root and

/functions

but no dice.

/*
  Access-Control-Allow-Origin: *

I'm testing in wrangler, but I haven't been able to get it working in production either

Needs to be in your build output directory (with your static assets) 🙂

ah ok, thanks

Did you manage to get it working? For me it's working for static assets but not functions.

I haven't had a chance; I misspelled

_headers

three times, then decided that maybe it was time to take a break

that might be intentional? if it's in your build folder, that would make sense

Yeah, might be intentional.

you can always fall back on a

ts
let headers = { 'content-type': 'application/json;charset=utf8', "Access-Control-Allow-Origin": "*" };
return new Response(body, { headers, status });

to make it real easy, you could implement that as a piece of middleware that runs

const res = await next()

then does the above to it ^

not sure if this should be in wrangler or here, but when I run

npx wrangler pages dev -- npm start

to serve a tailwind react-app and I open port 8788 in the browser wrangler crashes with "TypeError: Web Socket request did not return status 101 Switching Protocols response with Web Socket" I can serve the function on :8788/api and also static assets from react and the react app works as normal on port :3000

I'm trying to setup a function that rewrites all

/profile/:whatever

endpoints to

/profile/[profile].html

(generated by next.js), but i'm getting an http error 406 with this code. I've tried changing the pathname to

/profiles/[profile].html

, but that just caused a redirect loop back to

/profiles/[profile]

Hey 👋 I hope I'm in the right cannel here. I'm working on a small website (build with Vue JS 3) that requires some "API calls" to a few functions. Now I'm trying to optimize my (messy/PoC) code a bit and reduce duplicate code. I'm using a

config.json

for some basic configuration parameter in the frontend. Is it possible to use this file in a function too (using an

require

or

import

statement)?

ts
import config from "../config.json";

and

"resolveJsonModule": true

in your

tsconfig.json

(if you use TS) should be all that's necessary

Great, thank you 😊

I was just concerned about if it would work with the "functions" 🙈 -> Testing it always takes quite long 😐

Isn't Next.js creating a

/profile/[profile]/index.html

(and not a

/profile/[profile].html

)? If so, the following might work:

ts
  env.ASSETS.fetch(
    new Request(
      new URL("/profile/[profile]/", request.url).toString(),
      request
    )
  )

The trailing

/

was important IIRC. Also, your message has a mix of singular and plural `profile`/`profiles` - which could also the underlying issue.

Yes on windows 👍

I'm trying to raise awareness for this bug 😮‍💨 seems like it could be similar to a previous Windows related issue with wrangler: https://discord.com/channels/595317990191398933/799437470004412476/911936976209457162

It's definitely making a /profiles/[profile].html. It's meant to be plural, that was a mistake when writing the message

in fact without the function, going to /profiles/[profile] goes to the right page

I tried using cache (from workers) in functions, but I'm getting

[pages:err] SyntaxError: Unexpected reserved word

in wrangler. Is cache not supported?

what's the difference between env.ASSETS.fetch vs the normal fetch?