🚀 Feature Request: allow applying flags to non-primary workers in multiworker dev

[vlovich]

Which Cloudflare product(s) does this pertain to?

Miniflare

What versions are you using?

Wrangler 4.1.0

What operating system and version are you using?

Linux Arch

Please provide a link to a minimal reproduction

No response

Describe the Bug

Set up a service binding in the current wrangler.json

npx wrangler dev --define FOO:true --config wrangler.json --config ../other-service/wrangler.json

Add a console.log(FOO) at the top level of the scripts in each service - the outermost receives the define but the servicing binding does not and there's no way I can tell to do so other than generating a temporary wrangler.json for other-service that has the define set properly.

Please provide any relevant error logs

No response

[vlovich]

Wow, I think even define defined within the wrangler.json that's passed as a second --config are ignored.

[vlovich]

May be related, at least explains the second thing I noted I observed, it looks like the environment flag only applies to the top-level wrangler.json and the secondary one loads with the default unnamed environment.

[emily-shen]

Hey, currently we only apply cli flags to the first worker when running multiple workers in one wrangler dev session. I've converted this to a feature request to track adding flags to the non-primary worker.

[petebacondarwin]

I think we now support sending the --env flag to all the workers, right?

[vlovich]

I'll take your word for it. I don't have access to the project I was doing this for anymore