Question about initOpenNextCloudflareForDev

[vicb]

@dario-piotrowicz I noticed that Using vars defined in .dev.vars is printed multiple times with next dev, see for example the output in the examples/api app:

-> % pnpm dev

> api@0.1.0 dev /Users/vberchet/code/work/opennextjs-cloudflare/examples/api
> next dev

Using vars defined in .dev.vars
Using vars defined in .dev.vars
  ▲ Next.js 14.2.11
  - Local:        http://localhost:3000
  - Environments: .env.development

 ✓ Starting...
Using vars defined in .dev.vars
Using vars defined in .dev.vars
 ✓ Ready in 1546ms

I'm wondering if this is expected?

Do we start wrangler multiple times? If yex, would there be a way to start it only once?

[dario-piotrowicz]

oh, I didn't notice that, let me have a quick look 👍

[dario-piotrowicz]

There are two issues here, one is that next dev imports the module twice in two distinct processes, so we basically call wrangler's getPlatformProxy twice, I will open a PR for fixing that in a few minutes, I just need to copy over this piece of code we had in next-on-pages: shouldSetupContinue() (sorry I should have remembered and copied it over already in #265 😓).

The other issue is an actual upstream wrangler one, it looks like calling getPlatformProxy with a .dev.vars file present causes a double log of the Using vars defined in .dev.vars message: cloudflare/workers-sdk#7944 (I can also have a quick look into that there)

[dario-piotrowicz]

With #293 and #305 this issue is resolved for next dev

However we do get various Using vars defined in .dev.vars when building the application 😓: