Pooya Parsa

As another alternative approach we can think of different methods of runtime config expansion (via a util that is not _env_) so we don't add over complexity to "environment" definition...

> It would be nice not to hard-code the use of process.env, Usage of `process.env` is a (current) method of accessing standard "runtime environment variables" which varies per runtime and...

Splitting into subtopics: - Runtime `updateRuntimeXConfig` (~> https://github.com/unjs/nitro/issues/2427) - Build time utils (~> https://github.com/unjs/nitro/issues/2428) I strongly belive in making a new source/definition of environment variables (as proposed with `opts.env`) in...

> to 'preview' the resolved config I guess at least all common runtimes allow to modify environment variables by directly modifying their env object (`Deno.env.set` and `process.env` object) if testing...

@danielroe Shall we close PR and later continue discussing about this perhaps after `updateRuntimeConfig` util landed? 🙏🏼

Closing for triage. Followup: - runtime: https://github.com/unjs/nitro/issues/2427 - kit util: https://github.com/unjs/nitro/issues/2428

Thanks! Sorry for delay. I am thinking to move this feature directly to httpxy.

(sorry for delay, rewrite should be implemented in upstream but we might also type it in nitro + consider a serialzable rewrite for production, that's why keeping it open)

As of discussion in #1894, I think we might use raw methods of unstorage (behind a flag) also unstorage should automatically handle base64 transformation for drivers not supporting natively binary...

(was hoping to rebase with latest [undio](https://undio.unjs.io/) version to support at least all h3 binary types including streams. might delay to prioritize other reactors sorry for this delay it is...