you can use

exit 0

it's on the docs somewhere but it's a dumb bug and we wanna fix it

i missed that in the docs! thank you

ah, this seems to be the issue (other routes removed)

json
{
  "routes": {
    "GET /api/stop/search/near/:latitude]/[longitude": {
      "module": [
        "api/stop/search/near/[latitude]/[longitude].ts:onRequestGet"
      ]
    }
  },
  "baseURL": "/"
}

Hello everyone I've deployed a skeleton SvelteKit app to Pages. I wanted to test the functions bit, so I added a

functions

directory at the root level — the same level as

src

. On my preview app — or in local Wrangler — my root route is now no longer defined; it errors out with a 404. The only routes available are the routes from my functions. Any idea on this? I would like to have the SvelteKit app call functions from the

functions

folder

SvelteKit doesn't work with

functions

since it uses them internally (meaning if you try to create functions it overrides theirs).

I'd instead point you towards either: - SvelteKit Endpoints (anything you can do in Functions you can do in Endpoints) - or

@sveltejs/adapter-static

and

/functions

.

Right, I see. Cos reading through the Functions docs, it looked similar to what's possible with SvelteKit. Thanks for clarifying

Hi, I would like to know if we could blind secret variables to function in production in the mean time?

Are you talking about environment variables?

I meant the “encrypted” environment variables (like the one available on workers)

I'm working locally with wrangler@beta. Have set up my first pages project with functions. Have created a simple path to a users dir which contains an index.js. Calling fetch on the response of that route returns my index.html content. Not the response of the function

I imagine I have something seriously wrong in my concept of how this works?

No frameworks. Just an index.html that calls a index.js with one simple fetch get request.

Error in catch is

SyntaxError: Unexpected token < in JSON at position 0

That response is actually just the current page returned.

Are all web requests made through

fetch

forced to use HTTPS? I have a strange issue where I appear to receive the response from the

https

URL instead of the

http

one, even though my fetch request starts with

http://

I found my issue. And just a total too late in the day thing. I had my route in the wrong folder...

Thanks for chiming in though. I had also been wondering about how that situation might be handled.

Not currently, it's planned for once Functions are out of beta.

Are the limits like CPU time or duration the same for functions as for normal workers?

For now I believe they correspond to the Bundled Workers plan (50ms), but that may change once Functions are GA.

Ah ok, thank you!

I see thanks

is it possible that firebase's "functions" directory conflicts with cloudflare's? is it possible to change what the directory is called?

Yeah it looks like those do conflict, so I guess you would have to break it into two separate repos

hmm yeah maybe. i don't use cloudflare functions because of the subrequest limit, but i always have an error that im over my functions request limit. wonder what if cf is trying to do something with my firebase functions.

Yup.. they are probably trying to package those up and run them?

I believe you can configure what Firebase's functions directory is called

looks like you can - will report back tomorrow if this solves functions exceeding their limit