use wrangler-proxy for vite dev scenario

[gerhardcit]

See issue#1 discussion about Bindings while running wrangler pages dev.

[pirciualex]

Thank you for the solution, it works well for me. I just have one suggestion: I think it would be a good idea to update the README as well in order to explain how the process of starting the proxy works (and maybe add the command in a script inside package.json).

[gerhardcit]

I had more luck with cf-bindings-proxy. I've given up on wrangler-proxy

james-elicx/cf-bindings-proxy#43

[clibequilibrium]

I had more luck with cf-bindings-proxy. I've given up on wrangler-proxy

james-elicx/cf-bindings-proxy#43

hi could you update the PR then ? would be very useful.

Thank you

[dario-piotrowicz]

@gerhardcit I would suggest you to try the recently introduced Miniflare magic proxy 🙂

It should work quite well with your strategy, you can see how it works here: https://github.com/jculvey/svelte-cf-bindings-poc/blob/master/src/hooks.server.ts

(you basically create a Miniflare instance, take its bindings and simply set those as the platform's env)

[gerhardcit]

@gerhardcit I would suggest you to try the recently introduced Miniflare magic proxy 🙂

It should work quite well with your strategy, you can see how it works here: https://github.com/jculvey/svelte-cf-bindings-poc/blob/master/src/hooks.server.ts

(you basically create a Miniflare instance, take its bindings and simply set those as the platform's env)

Like this direction. Please advise on how we can get wrangler and Miniflare to use the same locally persisted db path?

jculvey/svelte-cf-bindings-poc#1

I found export declare const DEFAULT_PERSIST_ROOT = ".mf"; in
node_modules/.pnpm/[email protected]/node_modules/miniflare/dist/src/index.d.ts

that must be a option in the Miniflare constructor.

const mf = new Miniflare({
persistRoot: "same as wrangler......"

[dario-piotrowicz]

@gerhardcit what about the --persist-to flag?

Alternatively if that doesn't work for you how about changing the path miniflare uses by specifing a persistence with different path in the d1Persist option?

-    d1Persist: true,
+    d1Persist: '.wrangler/state/v3/d1',

[dario-piotrowicz]

that must be a option in the Miniflare constructor.

yes, but it's on a per-storage type basis (this is how I've applied it to our Next.js adapter for example)

[gerhardcit]

@dario-piotrowicz , thx. d1Persist: '.wrangler/state/v3/d1' does the trick.

This means no need for proxy in dev. This is super helpful!