easy5 pts · first answer countsnextjssecrets-management

Renaming a secret to NEXT_PUBLIC_

A client component shows undefined for process.env.STRIPE_SECRET_KEY, so a developer renames it to NEXT_PUBLIC_STRIPE_SECRET_KEY and it starts working. What is wrong?

A.Nothing, because NEXT_PUBLIC_ variables are encrypted inside the bundle and decrypted at runtimeB.It only works in development, not in productionC.The secret is now copied into the JavaScript bundle that anyone can downloadD.Environment variables cannot contain underscores

Discussion 0

Join free to post in the discussion.

Renaming a secret to NEXT_PUBLIC_

Discussion 0

Related questions