No but I managed to do something with this repo: github.com/zeit/next.js/tree/canar...
1) Create now.json and fill it like that :
{ "build": { "env": { "SECRET": "@my-secret-key", "ANOTHER_SECRET": "@my-other-secret-key" } } }
2) Then in your next.config.js you'll add module.exports:
module.exports = { env: { SECRET: process.env.SECRET, }, }
3) What worked for me at the end was to add my variables using "now secret add". I previously added my variable in the new variable UI on the website but it didn't work...
Hope this will help!
A workaround I found for now is to list all the variables you want in the client side code in the env property of the Next.js config.
env
env: { AUTH_SECRET: process.env.AUTH_SECRET, }
I updated the post with more details. In the example I linked at the end of the post, I didn't use any secrets.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
No but I managed to do something with this repo: github.com/zeit/next.js/tree/canar...
1) Create now.json and fill it like that :
2) Then in your next.config.js you'll add module.exports:
3) What worked for me at the end was to add my variables using "now secret add". I previously added my variable in the new variable UI on the website but it didn't work...
Hope this will help!
A workaround I found for now is to list all the variables you want in the client side code in the
envproperty of the Next.js config.I updated the post with more details. In the example I linked at the end of the post, I didn't use any secrets.