If you want it to be saved to the filesystem, you can add

--persist

too

And note that your local namespace will not be the same as your production one

Do the function deployment respect the kv_namespaces setting in wrangler.toml or how do I bind this in production?

You do this binding in the UI on Cloudflare for Pages. As far as I know wrangler.toml is ignored for Pages Functions.

Does Functions support Analytics Engine binding?

What is the best way for TypeScript to detect whether it is in browser or in the worker runtime ?

I was trying

typeof origin === 'string'

but it throws

Error: Failed to get the 'origin' property on 'ServiceWorkerGlobalScope'

That seemed perfect though 😦

navigator.userAgent === 'Cloudflare-Workers'

if your compatibility date is newer than

2022-03-21

will identify Workers specifically

thanks

Hi, I want to ask about local bindings. Is it the only way to bind KV namespaces or durable objects by using CLI arguments? Is there any plan to support

wrangler.toml

things for Cloudflare Pages? I guess this kind of question has already been asked much, but I'm new here 😅

Yes, and yes 😀 Support for config in some capacity is planned, such as wrangler.toml, but there’s no specifics or timeline yet as far as I know.

Thanks!

Same here, never get functions work for a Pages project

hi guys, i am not able to access KV locally? I am running wrangler using this command "wrangler pages dev -- npm run start --proxy=4000 --kv KV_Sample", but context.env.KV_Sample is coming undefined. Please help me with solution

duplicate of #874727019479437372

when using functions, will serving static assets still count to the usage? other question is what happens if a static asset and function have the same path. which one is served?

If your function is on a specific route such as

/functions/hello.js -> /hello

, you will only be billed for requests to /hello, regardless of whether there is an asset there or not, as the function takes priority

If you have one such as

/functions/api/[[path]].js -> /functions/api/*

, pages is unable to work out which routes you want your function to run on as easily, so any request under /api/* will rush your functions

ok for the assets question. if I have a static index.html at the base and functions for /api/[[path]] . will I also be billed for the

index.html -> /

requests

No, because pages knows you have no functions on that route

On the other hand, if you had

/functions/[[path]] -> /*

, it wouldn't know which routes are functions, and which aren't, so every request would be billed

is there a way I can make the static take priority

Unfortunately not

unless specified in _routes.json

but it only takes up to 100 entries

Yep

But that would entirely stop your function on that route, not just a serve the asset, or then the function if it's not there

I thought it would work like how a php website would work for example which it will try statuc assets first and if it doesn't find it it proxies the request to one index.php

it makes more sense to have static assets take priority or a bettwr solution would be a function 404.js