turbopack: ensure ENV values are available in middleware (#47767)
Turbopack starts up the router process with all ENV values, but the edge function definition didn't list any `env` keys for the function invocation. So, middleware couldn't access any ENV values. Turbopack doesn't currently have a way to determine what ENV keys are actually used by the source program, so I'm just passing everything defined. I'm not sure if that's an issue during dev (I could see it being one for the build process, but that doesn't matter for this case). Fixes #47766 Fixes WEB-831 Fixes WEB-834
Showing
Please
register
or
sign in
to comment