feat: make env setup work in middleware

[iduuck]

Is your feature request related to a problem? Please describe.

I am currently facing a problem, when using the environment variable setup from t3 and I am opening this issue, since the other issue about environment variables not working (#999) was closed by the author.

Describe the solution you'd like to see

It would be necessary (for now – don't know, if this is being fixed, though) to also compose the server env vars, like we do for the client env vars.

Describe alternate solutions

non that i can think of.

Additional information

No response

[c-ehrlich]

Could you explain more precisely what you are trying to do? Accessing env vars in middleware works just as it would anywhere else, see: c-ehrlich/mwenv@492bef2

[iduuck]

Sorry, not speaking of trpc middleware, but of Next.js middleware.

[c-ehrlich]

Just tried and can confirm that this currently doesn't work, the import makes Next middleware blow up. Accessing the environment variables in a non-typesafe way (ie process.env.SERVERVAR does work, but obviously isn't ideal.

What would we need to do to get it to work, and are there any downsides?

[iduuck]

I think the only way to work around this, is to define the server env vars the same way, as we do with the client env vars (explicitly building our env object before verifying).

[iduuck]

fixed by #1021