fix: pass auth profiles to vite

[emily-shen]

Fixes #14580

---

• Tests
  • Tests included/updated
  • Automated tests not possible - manual testing has been completed as follows: ran wrangler logout; wrangler auth profile create/activate 'test'; vite dev in a directory with remote bindings. no oauth flow triggered, remote bindings used the 'test' profile. then deleted profile, and it required re-authing.
  • Additional testing not necessary because:
• Public documentation
  • Cloudflare docs PR(s):
  • Documentation not necessary because: bugfix

A picture of a cute animal (not mandatory, but encouraged)

[changeset-bot]

🦋 Changeset detected

Latest commit: 3ede3c3

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

This PR includes changesets to release 3 packages

Name	Type
wrangler	Patch
@cloudflare/vite-plugin	Patch
@cloudflare/vitest-pool-workers	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

[ask-bonk]

Review posted successfully to PR #14588.

I reviewed the PR, which adds an import-time initProfileResolution() to the wrangler public API barrel to make the Vite plugin respect directory-activated auth profiles. I flagged 4 issues, ranked by severity:

1. (High) Resolving against process.cwd() instead of the config file's directory (as the CLI does) means the fix silently fails when Vite runs from a different directory than the wrangler config — reproducing the original bug. Included an inline suggestion to resolve lazily from the plugin using dirname(configPath).
2. (Medium) Import-time global side effect affects all consumers (including unstable_dev), doing filesystem reads and mutating the OAuth singleton on mere import.
3. (Medium) The doc comment about the yargs handler "overriding later" is misleading for the Vite consumer, which has no yargs handler.
4. (Low) Missing changeset and tests for a user-facing behavior change.

github run

[pkg-pr-new]

@cloudflare/autoconfig

npm i https://pkg.pr.new/@cloudflare/autoconfig@14588

create-cloudflare

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

@cloudflare/deploy-helpers

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

@cloudflare/kv-asset-handler

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

miniflare

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

@cloudflare/pages-shared

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

@cloudflare/unenv-preset

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

@cloudflare/vite-plugin

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

@cloudflare/vitest-pool-workers

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

@cloudflare/workers-auth

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

@cloudflare/workers-editor-shared

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

@cloudflare/workers-utils

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

wrangler

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

commit: a3f521c

[github-actions]

✅ All changesets look good

[workers-devprod]

Codeowners approval required for this PR:

• ✅ @cloudflare/wrangler

Show detailed file reviewers

[jamesopstad]

Is there some way we can test this so it doesn't regress or is it too difficult?

[workers-devprod]

Codeowners reviews satisfied