I would assume that the file would be generated locally during that? I am not too familiar with exactly how the bundling/compilation happens unfortunately..

seems to be doing it in memory, i don't see any files (besides what svelte generates)

wrangler pages dev

dumps it to a tmp directory

wrangler pages functions build

will generate an

_worker.js

in the cwd

Thanks

i am using functions not workers

Functions don’t run node either.

what are the time limits on functions currently, and will it change after the beta?

My script currently reads from our API server, and that query takes 20~200ms depending on the CF datacenter location

The time limits are the same as standard Bundled Workers. You get 50ms of CPU Time, which means that as long as you aren't doing a lot of processing in your Function, you should be fine.

does the HTTP query time also use up the 50ms limit?

(querying our API server from functions)

Creating the query does, but once the connection is initiated, the counter stops until you receive the response.

awesome! Thanks 😄

has anyone run into this on localhost? running

npx wrangler pages dev

i get it every OTHER time I refresh, which is very weird

Also, qq about this: > While still in open beta, there is no additional cost to deploy Functions within a Pages project. However, during beta, there is a total limit of 100,000 invocation requests per day. If you reach your daily limit, Pages will stop executing your Functions and fallback to serving only static assets. to make sure i'm understanding correctly—if the 100k limit is hit, the site won't break right? it'll just stop running the functions code, and instead serve assets as if the functions code didn't exist

Yup. The only problem is, some frameworks don’t really have servable static assets, like Remix. So, in that case, your site would break when you hit the limit

gotcha. for our use case, we're serving a CRA app, and use the cloudflare functions code just to write some custom meta tags. so it seems like even if we hit 100k it won't break

So yeah, for now, if it isn’t that important, it is fine. If the execution is mission critical, use Workers until Functions go GA

If your function is capturing all requests with

[[path.js]]

i would make sure to test exactly what happens after you hit 100k requests.

The behaviour at 100k is to forget about functions and serve the static files as if the functions never existed

Same behaviour you get when you have no functions directory

Are you using Remix by chance? Or have you implemented etag/if-none-match headers?

So if your site is static and the functions provide some additional enhancement, you’re fine. If you’re using remix, your site is down until tomorrow.

Yes. But for the use-case given above, this is fine.

I'm running into the following error when running

wrangler

for my Functions dev environment:

Error scanning for ports of process with PID 49615: Error: spawnSync /bin/sh ENOBUFS
Error scanning for ports of process with PID 49616: Error: spawnSync /bin/sh ENOBUFS
Error scanning for ports of process with PID 49617: Error: spawnSync /bin/sh ENOBUFS
Could not automatically determine proxy port. Please specify the proxy port with --proxy.

has anyone else run into this and have any suggestions on how to go about resolving it?

Written URLs in my API response are being changed from

http://

to

https://

? What's going on? I've read about URL rewriting and URL normalization.

This is using wrangler