Empty `NEXT_PUBLIC_*` environment variables are evaluated as `undefined` rather than as empty strings about next.js HOT 5 OPEN

Agreed, this bug silently broke redirection-links for us where we sometimes use different base-paths depending on the environment. I feel like we should be able to expect it to be evaluated as a string when set like one.
NEXT_PUBLIC_BASE_PATH=''

As a temporary fix we reverted to 14.1.4 in wait for a real fix

from next.js.

Nice catch! I've made a PR for it, hopefully it gets reviewed soon

from next.js.

It's pretty much an ordinary nextjs setup with NEXT_PUBLIC_BASE_PATH='' in .env, then I'm using it in a utilities function that's returning: ${window.location.origin}${process.env.NEXT_PUBLIC_BASE_PATH}, where it's then called from a function within a page component like: ${appURL()}${path} to create a url. All of which have worked fine before.

Alright, then yea I think this should also cover that.

from next.js.

Agreed, this bug silently broke redirection-links for us where we sometimes use different base-paths depending on the environment. I feel like we should be able to expect it to be evaluated as a string when set like one. NEXT_PUBLIC_BASE_PATH=''

As a temporary fix we reverted to 14.1.4 in wait for a real fix

@timlindsk hi, could you show us a small reproduction set of steps, or better yet a repository? I would like to verify that the proposed fix also fixes your issue.

from next.js.

It's pretty much an ordinary nextjs setup with NEXT_PUBLIC_BASE_PATH='' in .env, then I'm using it in a utilities function that's returning:
${window.location.origin}${process.env.NEXT_PUBLIC_BASE_PATH}, where it's then called from a function within a page component like: ${appURL()}${path} to create a url. All of which have worked fine before.

Sidenote, separate issue, while troubleshooting: I also stumbled upon an issue where compiling mui/icons-material ended up in a crash because "use strict"; was on top of "use client"; But I have yet to boil down the root of that problem, it seems to be related to a later version of nextjs, but I'm also not sure as what the best practice is regarding it, if they should be switched around by mui/icons-material I mean, or if nextjs should allow for it. Can't seem to find much about it other than the case where there's no "use client"; at all. Any pointer?

from next.js.