Issue when working with route.ts about next-runtime-env

[HofmannZ]

This is due to how nextjs' build process works. They still set the public envs to a static string if they are declared in your .env and prefixed with NEXT_PUBLIC_.

There are two solutions:

1. Remove the .env file.
2. Remove the NEXT_PUBLIC_ prefix.

If you choose option 2, and you need to access the env var on both the server and the client, you can use the makeEnvPublic utility to automatically create the prefixed variable.

Let me know if that helps ✌️

[HofmannZ]

I'm not able to reproduce your issue. To confirm I've added a route handler to the example.

You can try it out yourself:

1. Clone the repo
2. Checkout the development branch
3. cd to the example with-app-router
4. Run pnpm build
5. Run NEXT_PUBLIC_FOO=foo-value BAR=bar-value BAZ=baz-value pnpm start
6. Visit http://localhost:3000/api/bar-baz and see the values of the runtime env vars returned.

Can you check if your implementation differs from the example?

[bagelbits]

@HofmannZ I found where my implementation differs, but I don't know if this is working as intended.

Steps to replicate

1. Add a .env.local file:

NEXT_PUBLIC_FOO="yes"
BAR="hello"
BAZ="world"

2. Change examples/with-app-router/src/app/api/bar-baz to:

export async function GET() {
  return Response.json({
    bar: process.env.BAR,
    baz: process.env.BAZ,
    foo: process.env.NEXT_PUBLIC_FOO,
  });
}

export const dynamic = 'force-dynamic';

3. pnpm build
4. NEXT_PUBLIC_FOO=foo-value BAR=bar-value BAZ=baz-value pnpm start

Expected

{"bar":"bar-value","baz":"baz-value","foo":"foo-value"}

Actual

{"bar":"bar-value","baz":"baz-value","foo":"yes"}

[bagelbits]

@HofmannZ Amusingly, if you don't have the .env.local file, this works just fine. But it's inconsistent that .env.local overrides the NEXT_PUBLIC_* but not the normal ENV vars. Is that just the nature of how NEXT_PUBLIC_* works?

[bagelbits]

@HofmannZ That 100% worked! Thank you so much for the clarification!