Hacker News Reader

the biggest headache i had in particular was different ways of handling environment variables, but the different adapters at OpenNext have had a rolling list of caveats/unsupported features for as long as i've been following the project so i didn't want to outright say "full". hopefully the effort on Next's side to build a standardized adapter API will help with this!

View on HN

Ah, fair. That is an area we struggled with. We run next in kubernetes (GKE) and really wanted to be able to promote the Docker/OCI image up through our environments (ie: not bake environment variables into the build artifact). We settled on having them dumped in a meta tag in the root document, and then have some helper functions to access those. We still have to use process.env for any secrets though, which makes them inaccessible to the frontend code (but that's sort of the point).

Reply on news.ycombinator.com