does getPlatformProxy support the HYPERDRIVE binding yet? It's not pulling for me within my svelteki
does getPlatformProxy support the HYPERDRIVE binding yet? It's not pulling for me within my sveltekit hooks handler
HAccording to the docs, no: https://developers.cloudflare.com/workers/wrangler/api/#supported-bindings
Cloudflare Docs
A set of programmatic APIs that can be integrated with local Cloudflare Workers-related workflows.
Pis this source available somewhere? I was told this was all supported and just the UI needed updated
HBy whom? Also,
getPlatformProxy shouldn't require UI at all...
PHThat's specifically with Pages/dev, not with the
platformProxy, no?Pi have no idea, there are many layers here.
HI would guess it just isn't supported then atm
PGitHub
Which Cloudflare product(s) does this pertain to? Pages, Other What version(s) of the tool(s) are you using? Latest everything What version of Node are you using? 18.18.2 What operating system and ...
HThat appears to be related to deployment, not to the Platform Proxy
Pok, so the platform proxy is used during development only?
Pso i might just get lucky if i try to deploy...
HYeah, in fact, if you try building your project, then running it with
wrangler pages devit looks like it's pulling in my production binding, but i'm back to seeing " Your Worker may throw errors at runtime unless you enable the "nodejs_compat" compatibility flag." errors
Pwhich if i remember from this rabbit hole, nodejs_compat flag only applies to workers, and i am on a Cloudflare Pages Function
HNo, Functions do also support
nodejs_compatPI am getting these errors and the app fails to load: [ERROR] service core:user:worker: Uncaught Error: No such module "node:events".
HYou can provide it in your
wrangler.tomlYeah, you probably need
nodejs_compat thenPOk trying now...
Pwith
compatibility_flags = [ "nodejs_compat" ]i'll be damned it worked!
Pok, so it seems getPlatformProxy is just lagging behind a bit on the local development side...
Pi wonder how much of a patch would be needed to just add it, or if there is a way for me to patch it in now manually
Pwow,
wrangler pages devlocalConnectionString setting so i can test against the local db. Excellent.PHyperdrive no where to be found in this: https://github.com/cloudflare/workers-sdk/blob/main/packages/wrangler/src/api/dev.ts
R
has anybody got a good solution for storing and analysing logs from a cloudflare pages function?
Jdoesn't work
J
Wdeployment id?
Jwhere do I find that
J9feb8399-ddc5-473b-bf90-0776a8f7ca62JI think this is it
Jprobably something to do with all this node_compatability not actually working the same in Workers/Functions
Wweird that's internal erroring
Woutput_dir_outside_repo
Wpages_build_output_dir: ../../../dist
Wyeah that'll be why
Wthis is from your root
Jpages_build_output_dir = "/dist"Wso should just be "dist"
Jok
Woh it's resolving the / to be the linux root
Wthat's fun
Jit still prob won't deploy tho
Wwe should probably special case /
Jaa05a643-cab9-4d50-9524-e508b5600cf9Jyup, still the same errors as before,
nodejs_compat is not really what works. need the same node compatability flag as Workers
Wcan you raise an issue on https://github.com/cloudflare/workers-sdk/issues for this bug? We should get that fixed 
and thanks for finding this!
and thanks for finding this!
JProduct explicitly decided to not support node_compat due to it being our not recommended thing
