improve and test vite-plugin-cloudflare .dev.vars files support

[dario-piotrowicz]

fixes #7850

the changes here add tests for making sure that the vite plugin correctly reads secrets from .dev.vars files with and without a specified environment

as part of this wragler's unstable_getMiniflareWorkerOptions utility needed to also be updated to accept the environment name as its second parameter

---

• Tests
  • TODO (before merge)
  • Tests included (tests added for the vite-plugin, as for wrangler, it looks like the unstable_getMiniflareWorkerOptions utility is not currently tested, so I don't think it's necessary to include any here either)
  • Tests not necessary because:
• E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)
  • I don't know
  • Required
  • Not required because:
• Public documentation
  • TODO (before merge)
  • Cloudflare docs PR(s):
  • Documentation not necessary because: documentation added as part of our vite-plugin README (which is currently the only documentation the package has)

[changeset-bot]

🦋 Changeset detected

Latest commit: a39093d

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

This PR includes changesets to release 3 packages

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

[github-actions]

A wrangler prerelease is available for testing. You can install this latest build in your project with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13001188073/npm-package-wrangler-7864

You can reference the automatically updated head of this PR with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/7864/npm-package-wrangler-7864

Or you can use npx with this latest build directly:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13001188073/npm-package-wrangler-7864 dev path/to/script.js

Additional artifacts:

cloudflare-workers-bindings-extension:

wget https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13001188073/npm-package-cloudflare-workers-bindings-extension-7864 -O ./cloudflare-workers-bindings-extension.0.0.0-vc2ba65d44.vsix && code --install-extension ./cloudflare-workers-bindings-extension.0.0.0-vc2ba65d44.vsix

create-cloudflare:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13001188073/npm-package-create-cloudflare-7864 --no-auto-update

@cloudflare/kv-asset-handler:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13001188073/npm-package-cloudflare-kv-asset-handler-7864

miniflare:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13001188073/npm-package-miniflare-7864

@cloudflare/pages-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13001188073/npm-package-cloudflare-pages-shared-7864

@cloudflare/unenv-preset:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13001188073/npm-package-cloudflare-unenv-preset-7864

@cloudflare/vite-plugin:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13001188073/npm-package-cloudflare-vite-plugin-7864

@cloudflare/vitest-pool-workers:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13001188073/npm-package-cloudflare-vitest-pool-workers-7864

@cloudflare/workers-editor-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13001188073/npm-package-cloudflare-workers-editor-shared-7864

@cloudflare/workers-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13001188073/npm-package-cloudflare-workers-shared-7864

@cloudflare/workflows-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13001188073/npm-package-cloudflare-workflows-shared-7864

Note that these links will no longer work once the GitHub Actions artifact expires.

---

wrangler@3.105.1 includes the following runtime dependencies:

Package	Constraint	Resolved
miniflare	workspace:*	3.20250124.0
workerd	1.20250124.0	1.20250124.0
workerd --version	1.20250124.0	2025-01-24

Please ensure constraints are pinned, and miniflare/workerd minor versions match.

[jamesopstad]

Looks good! Just a few code comments and some changes to the readme.

[vicb]

Suggested change

	MY_DEV_VAR_A = "my .dev.vars staging variable A"
	MY_DEV_VAR_B = "my .dev.vars staging variable B"
	MY_DEV_VAR_A = "my .dev.vars.staging variable A"
	MY_DEV_VAR_B = "my .dev.vars.staging variable B"

[dario-piotrowicz]

I prefer not to have the . so that it is clearer that this this is a manually inputted string (otherwise without seeing the implementation someone could thing that this was generated by something like my ${devVarsFileName} variable A)

if you find it confusing I can change the strings to something like MY_DEV_VAR_A = "my .dev.vars variable A for the staging environment (or something like that)

[vicb]

Note, mostly unrelated to this PR:

The vite-plugin catalog pins @types/node but that will not work as expected because of

		"overrides": {
			// ...      
			"@types/node": "$@types/node"
		},

So there would need to be a more specific override there for the plugin package

[vicb]

is there any benefit in having a variable here (i.e. do we expect to add more files)
Otherwise it looks looks inlining would be less convoluted

[dario-piotrowicz]

the benefit of the variable are:

• it is nicer to have if we can indeed add more files in the future
• if is a self documenting variable, the variable name helps (at least to me) understanding that it does

those are not huge benefits I don't mind inlining the array if that's what you strongly prefer

[petebacondarwin]

I admit I am not convinced this needs a variable. But I don't care strongly.

[dario-piotrowicz]

me neither 😅, as I said I prefer having the variable but it's not a huge deal either way 🙂

[vicb]

Looks good - with my limited understanding of the plugin.

But I always find things to comment ;)

[petebacondarwin]

I admit I am not convinced this needs a variable. But I don't care strongly.