[wrangler] Fix circular dependency build warning in cli.ts

[emily-shen]

Import convertConfigBindingsToStartWorkerBindings directly from ./api/startDevWorker/utils instead of through the ./api barrel to break a circular chunk dependency that Rollup warns about during the DTS build.

The cycle was:

1. api/index.ts re-exports from startDevWorker/utils.ts
2. startDevWorker/utils.ts type-imports from ../../dev.ts
3. dev.ts type-imports from ./api (back to step 1)

I think it was an explicit decision to export from "api/index.ts" but it seems a bit difficult to preserve that without making invasive changes that are probably going to give incoming refactors some bad merge conflicts...

---

• Tests
  • Tests included/updated
  • Automated tests not possible - manual testing has been completed as follows:
  • Additional testing not necessary because: build-only warning fix, no runtime behavior change
• Public documentation
  • Cloudflare docs PR(s):
  • Documentation not necessary because: internal build fix

---

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1f697ba

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[workers-devprod]

Codeowners approval required for this PR:

• @cloudflare/wrangler

Show detailed file reviewers

• packages/wrangler/src/cli.ts: [@cloudflare/wrangler]
• packages/wrangler/src/dev.ts: [@cloudflare/wrangler]

[ask-bonk]

The remaining ./api imports at lines 11-25 are still value imports (DevEnv, getPlatformProxy, etc.), and line 43 is type-only. So cli.ts still imports values from the ./api barrel — the barrel itself still re-exports from startDevWorker/utils at api/index.ts:20.

This is worth noting: the change only removes one value import from cli.ts, but cli.ts continues to import other values from ./api, and the barrel still re-exports the function. Whether this actually breaks the Rollup DTS chunk cycle depends on Rollup's chunking, which is plausible for the DTS build. The change is low-risk and behavior-preserving regardless. No actionable correctness issue.

The change is correct, minimal, behavior-preserving, and the public API surface is unchanged. No logic bugs, security issues, or compatibility concerns.

LGTM

github run

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.

[pkg-pr-new]

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@14197

@cloudflare/deploy-helpers

npm i https://pkg.pr.new/@cloudflare/deploy-helpers@14197

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@14197

miniflare

npm i https://pkg.pr.new/miniflare@14197

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@14197

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@14197

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@14197

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@14197

@cloudflare/workers-auth

npm i https://pkg.pr.new/@cloudflare/workers-auth@14197

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@14197

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@14197

wrangler

npm i https://pkg.pr.new/wrangler@14197

@cloudflare/wrangler-bundler

npm i https://pkg.pr.new/@cloudflare/wrangler-bundler@14197

commit: 1f697ba

[petebacondarwin]

Would an alternative approach be to move AdditionalDevProps into src/api/StartDevWorker?

Or rather than "picking" from it in startDevWorker/utils.ts to define StartDevOptionsBindings, we just define the interface explicitly? And maybe even then extending StartDevOptionsBindings when defining the AdditionalDevProps interface?