Provide mechanism for autopopulating node.js process.env

[jasnell]

Autopopulates the process.env from bindings in local dev. A similar PR will be needed internally to enable it there as it won't be automatic.

See caveats: #3311 (comment)

[vicb]

@irvinebroque can we discuss this?

I oppose this change of it exposed secrets to the world via process.env

[jasnell]

I oppose this change of it exposed secrets to the world via process.ENV

To be clear... the change puts any TEXT binding on process.env. We have no way of knowing if a a TEXT binding contains something that is considered a secret or not. If tooling insists on adding secrets to the worker configuration using a TEXT binding then this would mean we just cannot populate process.env automatically at all right now because we have zero ability to differentiate if the value of the TEXT binding is secret or not.

[jasnell]

Moved back to draft due to continued backend discussion on how the implementation intersects with non-nodejs-compat related aspects of the runtime.

Objection is noted but decision has been made to move forward.

[jasnell]

Rebased the PR and expanded comments. Maintained the existing implementation approach. If it becomes necessary it ought to be able to further change the underlying implementation details without breaking changes. The hypothetical case around how to handle potential new binding types that evaluate to strings can be addressed separately later when they are no longer hypothetical. An internal PR is necessary.

[irvinebroque]

👍 let's find a way to ship

Current approach meets the immediate need. Hypothetical additional cases can be looked at separately later.

[vicb]

Could a doc PR be prepared for this change?

[jasnell]

There already is a doc PR cloudflare/cloudflare-docs#19187

[vicb]

What are the plans regarding:

Autopopulates the process.env from bindings in local dev. A similar PR will be needed internally to enable it there as it won't be automatic.

When this will be activated on EW? When can this be enabled?

Does wrangler needs to be updated to support the flag/CLI options, is there a tracking issue?