Allow CI Workflow Run

• approve CI run for commit: 167a14e

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

There may be npm libraries who expect public vars prefixed as NEXT_PUBLIC_. If an app is configured with different prefix, these libraries won't work correctly. Even though NEXT_PUBLIC_ is somewhat verbose, it’s not confusing because it’s the same for everyone. Customisation can bring more confusion and complexity IMHO.

There may be npm libraries who expect public vars prefixed as NEXT_PUBLIC_. If an app is configured with different prefix, these libraries won't work correctly. Even though NEXT_PUBLIC_ is somewhat verbose, it’s not confusing because it’s the same for everyone. Customisation can bring more confusion and complexity IMHO.

What about allowing multiple prefixes? With NEXT_PUBLIC_ always being included. This way libraries with NEXT_PUBLIC_ are still working + can everyone configure their own prefix (even libraries)

Confusion begins when you ship your app built on top of Next.js, and users have no idea what NEXT_PUBLIC_ is. For that reason, there should be a way to rename it to something like MYAPP_PUBLIC_. Libraries that rely on hardcoded NEXT_PUBLIC_ will have to be updated. Indeed, this can be a breaking change, but that should not stop us from merging it.