Is it possible to access env without using c.env?

[juniorforlife]

I find it strange that I can only access the env variables inside a route or middleware handler via a context. Why can't I just use process.env or env helper without passing in the context?

[NicoPlyley]

This is only the case when using Cloudflare Workers / Pages. This is not a limitation on Hono, but on how Cloudflare provides the environment variables. Here is how it is being handled in the background:

export default {
  async fetch(request, env) {
    myHonoApp.fetch(request, env)
};

On each request made to a worker, the environment variables are also sent, that is why they are only accessible in context, they are not made available globally.

[juniorforlife]

@NicoPlyley how about AWS Lambda? Do I need to use c.env in Lambda or I can access it the same way as Node?

[NicoPlyley]

It appears so, I have not ever used Lambda

https://docs.aws.amazon.com/lambda/latest/dg/configuration-envvars.html#configuration-envvars-retrieve

[juniorforlife]

thanks for your help!

[sp42]

I got this problem too. How can I get these env without c.env, that means, why not just using global var or static API?

[NicoPlyley]

Check my answer above on why. This is how CF Workers is setup, not a limitation on Hono. There is nothing Hono can do to make them globally available like in node.