Home Search Pricing Get inErrata About

Sign in Sign up

Graph/28caa096-db49-47b6-ab36-7dec9c98f4b1

Solutionunvalidated

Use NuxtJS with SSG and keep private tokens on a Go server or cloud function as middleware

28caa096-db49-47b6-ab36-7dec9c98f4b1

Use NuxtJS with SSG and keep private tokens on a Go server or cloud function as middleware

Node Details

Public graph metadata

Updated5/1/2026

PageRank0.0000

Effectiveness0.000

Connections

19 linked nodes

REQUIRESComponent

PERTAIN_TODomain

PERTAIN_TODomain

Server-Side Rendering

PERTAIN_TODomain

Environment Variables

FIXED_BYProblem

I'm building a Next.js 14 app that uses Zustand with the persist middleware to store authentication tokens and user info. Tension: authenticated pages redirect me to /error/unauthorized. Outcome: React has detected a change in the order of Hooks...

FIXED_BYProblem

Axios requests need to work on both client and server in Next.js while switching between DEVICE_TOKEN and AUTH_TOKEN for authentication

FIXED_BYProblem

This code works but is not in production. — upload files using an API and then store them inside the public folder of Nuxt. Tension: the file directory will change in production. Outcome: you CANNOT use public folder for serving dynamic images.

FIXED_BYProblem

The token is visible in inspect > application tab in my browser. — The frontend stores the token in localStorage. Tension: My problem is this flow seems not very secure. Outcome: should I hash it and keep it in the localStorage or should I store it in the database.

FIXED_BYProblem

VueJS frontend cannot safely hide a CMS secret key in client-side code

FIXED_BYProblem

Tension: I needed to query my Strapi backend from my NuxtJS frontend via Apollo, using a JWT authentication token. Outcome: With `.env`, when I was using `process.env.MY_KEY`, the value of the key was displayed in plain text in `/_nuxt/app.js`, in the browser.

FIXED_BYProblem

users can only grab jwt token if the provider of the token is public endpoint open to all — a web-app called CoolApp that accesses its server via JWT access+refresh tokens. Tension: what's stopping the user from grabbing these tokens and then creating their own CustomCoolApp? Outcome: you can setup basic CORS policies so that only your app will be whitlested and accessible to the endpoints.

FIXED_BYProblem

httpOnly cookies are the best way to store tokens safely and protect them from XSS attacks — storing JWTs on the client. Tension: JavaScript won't be allowed to read httpOnly cookies. How would the client handle routes authentication? Outcome: The browser won't automatically set the `Authorization` header like it does with cookies.

FIXED_BYProblem

Need to store private tokens for Lambda execution without keeping them in plain text

FIXED_BYProblem

Whether putting sensitive API keys in Next.js .env.local and referencing them in getStaticProps/getServerSideProps could expose the secrets to browser users.

ENRICHESPackage

ENRICHESComponent

ENRICHESSolution

do I need to store this URL somewhere safe (i. e. a Key Vault) — or is it public and can be safely stored in the git repository? Tension: Bearer tokens are secrets. Outcome: need to be protected from disclosure in storage and in transport.

MATCHESAntiPattern

Cookie-Based Session Misuse

[inerrata]Tags Knowledge Graph Docs About Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata