fix: prevent duplicate warning messages in wrangler dev (v3 backport)

[devin-ai-integration]

Backport of #10913 to v3-maintenance branch.

Fixes #6855

This PR addresses duplicate warning messages during wrangler dev by changing all logger.warn() calls to logger.once.warn() in ConfigController.ts. When configuration is updated multiple times (common during development), the same warnings would be displayed repeatedly, creating noise in the console output.

Changes

ConfigController.ts: Updated 4 warning scenarios to use logger.once.warn():

• Live Services warnings in remote mode
• Upstream Protocol warnings for non-secure origins
• Queues warnings in remote mode
• SQLite in Durable Objects warnings in remote mode

ConfigController.test.ts: Added test to verify warnings are only logged once across multiple config updates.

Testing Notes

⚠️ Unable to test locally: Due to pre-existing environment issues in v3-maintenance branch (lint/build errors), local verification was not possible. Changes will need to be verified via CI.

Review Checklist

• Verify all 4 warning types are appropriate for once-only logging behavior
• Confirm the test actually reproduces the duplicate warning issue
• Check that manual backport correctly matches original PR Fix duplicate warning messages in wrangler dev #10913 implementation
• Verify CI passes since local testing wasn't possible

---

• Tests
  • Tests included
• Wrangler E2E Tests CI Job required?
  • Not required because: Internal logging behavior change
• Public documentation
  • Documentation not necessary because: Internal logging behavior change, no user-facing API changes

Link to Devin run: https://app.devin.ai/sessions/fe4aed656c5945a7adaa0078b1e9e9a8
Requested by: [email protected]

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[changeset-bot]

🦋 Changeset detected

Latest commit: fca9859

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
wrangler	Patch

Not sure what this means? Click here to learn what changesets are.

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

[emily-shen]

update this to match the original PR again

[devin-ai-integration]

Hi @emily-shen,

I've reviewed the original PR #10913 to match it exactly. The original PR includes changes to dev.test.ts that add a beforeEach hook calling logger.clearHistory() to the "containers" describe block for test isolation.

However, I've discovered that the v3-maintenance branch's dev.test.ts file doesn't contain a "containers" describe block at all (the file is 1984 lines vs 2209 on main). The containers tests don't exist in v3-maintenance, so those specific changes cannot be directly applied.

The current backport includes:

1. ✅ ConfigController.ts changes (logger.warn → logger.once.warn)
2. ✅ ConfigController.test.ts changes (test for warning suppression)
3. ❌ dev.test.ts changes (can't apply - containers describe block doesn't exist in v3-maintenance)
4. ✅ .changeset file

Should I:

• Leave the backport as-is without the dev.test.ts changes (since the containers tests don't exist in v3-maintenance)?
• Add logger.clearHistory() somewhere else in v3-maintenance's test files?
• Something else?

Please let me know how you'd like me to proceed. Thanks!

[emily-shen]

Ignoring the dev.test.ts changes is fine. The test in configcontroller.test.ts is not the same as in the original PR - it should be using the analytics engine binding

[holopin-bot]

Congratulations @devin-ai-integration[bot], the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cmhaf3w9000g0l404d767qwqf

This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account.
Or if you're new to Holopin, you can simply sign up with GitHub, which will do the trick!