Svelte 5 - Neon Auth, env file uses NEXT..._STACK_ instead of STACK_(env variable here)

So with neon setup through vercel. I noticed that the default keys imported into the env files are listed as:

NEXT_PUBLIC_STACK_PROJECT_ID 
NEXT_PUBLIC_STACK_PUBLISHABLE_CLIENT_KEY

NEXT_PUBLIC_STACK_PROJECT_ID 
NEXT_PUBLIC_STACK_PUBLISHABLE_CLIENT_KEY

Despite the neon auth documentation stating to use the keys:

# Neon Auth environment variables for JavaScript/Node
STACK_PROJECT_ID=YOUR_NEON_AUTH_PROJECT_ID
STACK_PUBLISHABLE_CLIENT_KEY=YOUR_NEON_AUTH_PUBLISHABLE_KEY
STACK_SECRET_SERVER_KEY=YOUR_NEON_AUTH_SECRET_KEY

# Neon Auth environment variables for JavaScript/Node
STACK_PROJECT_ID=YOUR_NEON_AUTH_PROJECT_ID
STACK_PUBLISHABLE_CLIENT_KEY=YOUR_NEON_AUTH_PUBLISHABLE_KEY
STACK_SECRET_SERVER_KEY=YOUR_NEON_AUTH_SECRET_KEY

So I'm wondering if that'll cause any issues?

1 Reply

adverse-sapphire•5w ago

Hey! No it will not cause any issues. The StackAuth SDK is still able to pick up these variables.

Gaming

Programming

Svelte 5 - Neon Auth, env file uses NEXT..._STACK_ instead of STACK_(env variable here)

Did you find this page helpful?