[BUG] TypeScript Binding Generation doesn't work

[wesbos]

Describe the bug

I'm using npx wrangler types --experimental-include-runtime to generate my binding types, which creates a worker-configuration.d.ts file in the root of my project that looks like this:

// Generated by Wrangler by running `wrangler types --experimental-include-runtime`

interface Env {
	OG: KVNamespace;
	DB: D1Database;
	ASSETS: Fetcher;
}

Now the types for (await getCloudflareContext()).env. look like this

Because this package ships then like this:

declare global {
    interface CloudflareEnv {
        NEXT_CACHE_WORKERS_KV?: KVNamespace;
        ASSETS?: Fetcher;
    }
}

If I rename the generated types to CloudflareEnv I see everything:

So either this package or the wrangler types command need to agree on the Env / CloudflareEnv naming?

Steps to reproduce

see above

Expected behavior

see above

@opennextjs/cloudflare version

0.3.4

Wrangler version

3.99.0

next info output

15.1.2

Additional context

No response

[vicb]

The cf-typegen npm script generated by the template is wrangler types --env-interface CloudflareEnv env.d.ts.

You can use wrangler types --experimental-include-runtime --env-interface CloudflareEnv env.d.ts

Leaving this open until we improve the doc

[wesbos]

ahh awesome thank you!

[vicb]

Sent a PR to the docs