[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"site-settings":3,"blog-post:nuxt-middleware-explained":8,"site-content":30,"blog-comments:ddd55ce1-48fd-40b4-ae91-48a6bec20a2a":252,"blog-posts-latest:24":253},{"id":4,"accent_theme":5,"font_theme":6,"updated_at":7},1,"midnight","saas","2026-10-28T07:05:59.308034+00:00",{"id":9,"title":10,"slug":11,"excerpt":12,"content":13,"cover_image":14,"meta_title":15,"meta_description":16,"og_image":17,"tags":18,"status":24,"published_at":25,"view_count":26,"deleted_at":27,"deleted_reason":17,"created_at":28,"updated_at":29},"ddd55ce1-48fd-40b4-ae91-48a6bec20a2a","Nuxt Middleware Explained — Auth, Redirects & Route Guards Deep Dive","nuxt-middleware-explained","Nuxt middleware runs before a page loads so you can check auth, redirect users, or block a route — on the server for the first hit and in the browser on later navigations.","\u003Ch2>Quick Answer\u003C\u002Fh2>\n\u003Cp>Nuxt middleware is code that runs \u003Cstrong>before a page finishes navigating\u003C\u002Fstrong>. Use it to check login, redirect guests, rewrite paths, or stop a navigation early. On the first visit it can run during SSR; on later client clicks it runs in the browser. Put “gatekeeper” logic here — not charts, not DOM work, and not secrets that belong only on the server API.\u003C\u002Fp>\n\n\u003Ch2>Quick Facts\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Topic:\u003C\u002Fstrong> Nuxt middleware (route guards)\u003Cbr>\n\u003Cstrong>Category:\u003C\u002Fstrong> Nuxt.js \u002F Routing &amp; Auth\u003C\u002Fp>\n\n\u003Ch2>Table of Contents\u003C\u002Fh2>\n\u003Cul>\n  \u003Cli>What Is Nuxt Middleware?\u003C\u002Fli>\n  \u003Cli>Why It Matters\u003C\u002Fli>\n  \u003Cli>How It Works\u003C\u002Fli>\n  \u003Cli>Step-by-Step Guide\u003C\u002Fli>\n  \u003Cli>Real Example\u003C\u002Fli>\n  \u003Cli>Pros &amp; Cons\u003C\u002Fli>\n  \u003Cli>Best Practices\u003C\u002Fli>\n  \u003Cli>Common Mistakes\u003C\u002Fli>\n  \u003Cli>FAQs\u003C\u002Fli>\n  \u003Cli>Key Takeaways\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>What Is Nuxt Middleware?\u003C\u002Fh2>\n\u003Cp>Think of middleware as a \u003Cstrong>security\u002Fcheckpoint guard\u003C\u002Fstrong> at the door of a page. The visitor asks for \u003Ccode>\u002Fadmin\u003C\u002Fcode>. Before the admin UI mounts, Nuxt runs your middleware. The guard can say “go in,” “go to login,” or “stop.”\u003C\u002Fp>\n\u003Cp>In Nuxt 3\u002F4 this usually means \u003Cstrong>route middleware\u003C\u002Fstrong> via \u003Ccode>defineNuxtRouteMiddleware\u003C\u002Fcode> in the \u003Ccode>middleware\u002F\u003C\u002Fcode> folder (or inline on a page). That is different from Nitro \u003Cem>server\u003C\u002Fem> middleware under \u003Ccode>server\u002Fmiddleware\u003C\u002Fcode>, which runs on every API\u002Fserver request. This article focuses on \u003Cstrong>route middleware\u003C\u002Fstrong> — the one you use for pages, layouts, and SPA-style navigations — and calls out server middleware only where people mix them up.\u003C\u002Fp>\n\u003Cp>If you already read \u003Ca href=\"\u002Fblog\u002Fnuxt-lifecycle-explained\">Nuxt Lifecycle Explained\u003C\u002Fa>, middleware sits in that timeline \u003Cem>after\u003C\u002Fem> the route is matched and \u003Cem>before\u003C\u002Fem> the page is fully shown with its final navigation result.\u003C\u002Fp>\n\n\u003Ch2>Why It Matters\u003C\u002Fh2>\n\u003Cul>\n  \u003Cli>\u003Cstrong>Auth that runs early\u003C\u002Fstrong> — users never flash a protected page for a second before redirect.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>One place for rules\u003C\u002Fstrong> — “must be logged in,” “must be admin,” “must finish onboarding” stay out of messy page templates.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>SSR-aware gates\u003C\u002Fstrong> — first HTML request can redirect on the server, which is better for SEO and security UX.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Consistent client navigations\u003C\u002Fstrong> — the same rules apply when users click \u003Ccode>NuxtLink\u003C\u002Fcode> inside the app.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Cleaner pages\u003C\u002Fstrong> — pages focus on UI and data; middleware focuses on access.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>How It Works\u003C\u002Fh2>\n\u003Cp>Middleware is part of Nuxt’s navigation pipeline. Simplified flow:\u003C\u002Fp>\n\u003Col>\n  \u003Cli>\u003Cstrong>Route match\u003C\u002Fstrong> — Nuxt knows which page (and layout) you want.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Middleware list builds\u003C\u002Fstrong> — global → named (from page\u002Flayout meta) → any inline middleware, in a defined order.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Each middleware runs\u003C\u002Fstrong> — you receive \u003Ccode>to\u003C\u002Fcode> and \u003Ccode>from\u003C\u002Fcode> route objects.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>You return a decision\u003C\u002Fstrong> — nothing (continue), \u003Ccode>navigateTo(...)\u003C\u002Fcode> (redirect), or \u003Ccode>abortNavigation(...)\u003C\u002Fcode> (cancel).\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Page continues\u003C\u002Fstrong> — only if every middleware allows it; then data fetching \u002F render continue in the lifecycle.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Important mental model:\u003C\u002Fp>\n\u003Cul>\n  \u003Cli>\u003Cstrong>First load \u002F refresh\u003C\u002Fstrong> — middleware can run on the \u003Cstrong>server\u003C\u002Fstrong> (SSR). No \u003Ccode>window\u003C\u002Fcode>, no \u003Ccode>localStorage\u003C\u002Fcode> unless you guard with \u003Ccode>import.meta.client\u003C\u002Fcode>.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>In-app navigation\u003C\u002Fstrong> — middleware runs on the \u003Cstrong>client\u003C\u002Fstrong>.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Same code file\u003C\u002Fstrong> — often one middleware must be safe in both environments.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Types you’ll use:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n  \u003Cli>\u003Cstrong>Global\u003C\u002Fstrong> — filename ends with \u003Ccode>.global.ts\u003C\u002Fcode> (example: \u003Ccode>middleware\u002Fauth.global.ts\u003C\u002Fcode>). Runs on every route change.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Named\u003C\u002Fstrong> — \u003Ccode>middleware\u002Fauth.ts\u003C\u002Fcode> → use as \u003Ccode>definePageMeta({ middleware: 'auth' })\u003C\u002Fcode>.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Inline\u003C\u002Fstrong> — anonymous function in \u003Ccode>definePageMeta({ middleware: [defineNuxtRouteMiddleware(...)] })\u003C\u002Fcode> for one-off rules (keep rare).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Route middleware vs server middleware:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n  \u003Cli>\u003Cstrong>Route middleware\u003C\u002Fstrong> — pages\u002Flayouts, auth redirects, A\u002FB routing UX.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Server middleware (\u003Ccode>server\u002Fmiddleware\u003C\u002Fcode>)\u003C\u002Fstrong> — every HTTP hit to Nitro (APIs, headers, logging). Do not put Vue page redirects only there and expect identical SPA behavior.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>Step-by-Step Guide\u003C\u002Fh2>\n\n\u003Ch3>Step 1: Create a named middleware\u003C\u002Fh3>\n\u003Cp>Add \u003Ccode>middleware\u002Fauth.ts\u003C\u002Fcode>:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>export default defineNuxtRouteMiddleware((to) =&gt; {\n  const session = useSupabaseSession() \u002F\u002F example — use your auth source\n\n  if (!session.value &amp;&amp; to.path.startsWith('\u002Fadmin')) {\n    return navigateTo('\u002Fadmin\u002Flogin')\n  }\n})\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Keep the function small: read state → decide → return redirect or nothing.\u003C\u002Fp>\n\n\u003Ch3>Step 2: Attach it to pages (or make it global)\u003C\u002Fh3>\n\u003Cp>On a protected page:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>definePageMeta({\n  middleware: 'auth',\n})\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Multiple middlewares (order matters — left to right \u002F array order):\u003C\u002Fp>\n\u003Cpre>\u003Ccode>definePageMeta({\n  middleware: ['auth', 'onboarding'],\n})\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>For rules that must run everywhere, rename to \u003Ccode>auth.global.ts\u003C\u002Fcode>. Global middleware is powerful — and easy to overuse. Prefer named middleware when only a few routes need the gate.\u003C\u002Fp>\n\n\u003Ch3>Step 3: Redirect and abort the Nuxt way\u003C\u002Fh3>\n\u003Cul>\n  \u003Cli>\u003Cstrong>\u003Ccode>return navigateTo('\u002Flogin')\u003C\u002Fcode>\u003C\u002Fstrong> — send the user elsewhere. Prefer \u003Ccode>return\u003C\u002Fcode> so navigation waits on it.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>\u003Ccode>return navigateTo('\u002Flogin', { replace: true, redirectCode: 302 })\u003C\u002Fcode>\u003C\u002Fstrong> — useful on SSR redirects.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>\u003Ccode>return abortNavigation()\u003C\u002Fcode>\u003C\u002Fstrong> or \u003Ccode>abortNavigation(error)\u003C\u002Fcode> — cancel this navigation (stay \u002F show error depending on context).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Avoid raw \u003Ccode>window.location = ...\u003C\u002Fcode> inside middleware unless you intentionally want a hard browser reload.\u003C\u002Fp>\n\n\u003Ch3>Step 4: Make it SSR-safe\u003C\u002Fh3>\n\u003Cp>Ask: “Will this run on the server on first paint?”\u003C\u002Fp>\n\u003Cul>\n  \u003Cli>Read cookies \u002F server-known session — good on SSR.\u003C\u002Fli>\n  \u003Cli>Read \u003Ccode>localStorage\u003C\u002Fcode> only — breaks or lies on SSR (empty on server, filled on client → hydration\u002Fauth flicker).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Pattern:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>export default defineNuxtRouteMiddleware((to) =&gt; {\n  if (import.meta.server) {\n    \u002F\u002F cookie \u002F server session check\n  }\n  if (import.meta.client) {\n    \u002F\u002F optional client-only enrichment\n  }\n})\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>For real security, never rely on middleware alone: protect APIs and server routes too. Middleware is a UX + soft gate; server auth is the hard gate.\u003C\u002Fp>\n\n\u003Ch3>Step 5: Pass context with route meta (optional but deep)\u003C\u002Fh3>\n\u003Cp>You can mark pages and read flags in middleware:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F\u002F page\ndefinePageMeta({\n  middleware: 'auth',\n  roles: ['admin'],\n})\n\n\u002F\u002F middleware\nexport default defineNuxtRouteMiddleware((to) =&gt; {\n  const roles = to.meta.roles as string[] | undefined\n  \u002F\u002F compare to user roles…\n})\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This keeps one middleware reusable across many pages with different rules.\u003C\u002Fp>\n\n\u003Ch3>Step 6: Test both first load and in-app clicks\u003C\u002Fh3>\n\u003Col>\n  \u003Cli>Open protected URL in a new tab (SSR path).\u003C\u002Fli>\n  \u003Cli>Click from a public page to the protected page (client path).\u003C\u002Fli>\n  \u003Cli>Confirm no “flash of admin UI,” and redirect target is correct both times.\u003C\u002Fli>\n\u003C\u002Fol>\n\n\u003Ch2>Real-World Example\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Portfolio admin area\u003C\u002Fstrong> (same pattern as many Nuxt + Supabase apps, including setups like this site’s \u003Ca href=\"\u002Fblog\">blog\u003C\u002Fa> admin):\u003C\u002Fp>\n\u003Cul>\n  \u003Cli>Public pages: \u003Ccode>\u002F\u003C\u002Fcode>, \u003Ccode>\u002Fblog\u003C\u002Fcode>, \u003Ccode>\u002Fabout\u003C\u002Fcode> — no auth middleware.\u003C\u002Fli>\n  \u003Cli>\u003Ccode>\u002Fadmin\u002F**\u003C\u002Fcode> — must be logged in.\u003C\u002Fli>\n  \u003Cli>\u003Ccode>\u002Fadmin\u002Flogin\u003C\u002Fcode> — guests allowed; logged-in users maybe redirect to dashboard.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Named middleware sketch:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>export default defineNuxtRouteMiddleware((to) =&gt; {\n  const session = useSupabaseSession()\n  const isAdmin = to.path.startsWith('\u002Fadmin')\n  const isLogin = to.path === '\u002Fadmin\u002Flogin'\n\n  if (isAdmin &amp;&amp; !isLogin &amp;&amp; !session.value) {\n    return navigateTo('\u002Fadmin\u002Flogin')\n  }\n\n  if (isLogin &amp;&amp; session.value) {\n    return navigateTo('\u002Fadmin')\n  }\n})\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Before:\u003C\u002Fstrong> each admin page checked auth in \u003Ccode>onMounted\u003C\u002Fcode> → guests saw a blank admin shell, then bounced.  \n\u003Cstrong>After:\u003C\u002Fstrong> middleware redirects before the protected page becomes the active route — cleaner and closer to how the \u003Ca href=\"\u002Fblog\u002Fnuxt-lifecycle-explained\">Nuxt lifecycle\u003C\u002Fa> expects gates to run.\u003C\u002Fp>\n\n\u003Ch2>Pros &amp; Cons\u003C\u002Fh2>\n\u003Ch3>Advantages\u003C\u002Fh3>\n\u003Cul>\n  \u003Cli>Early, consistent access control across SSR and client navigations\u003C\u002Fli>\n  \u003Cli>Reusable rules via named middleware + \u003Ccode>definePageMeta\u003C\u002Fcode>\u003C\u002Fli>\n  \u003Cli>Keeps pages thinner and easier to maintain\u003C\u002Fli>\n  \u003Cli>Works naturally with \u003Ccode>navigateTo\u003C\u002Fcode> redirects\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Disadvantages\u003C\u002Fh3>\n\u003Cul>\n  \u003Cli>Easy to write browser-only code that breaks on first SSR request\u003C\u002Fli>\n  \u003Cli>Global middleware can slow or complicate every navigation if overused\u003C\u002Fli>\n  \u003Cli>Not a replacement for API\u002Fserver authorization\u003C\u002Fli>\n  \u003Cli>Debugging order (global + many named) takes care\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>Best Practices\u003C\u002Fh2>\n\u003Cul>\n  \u003Cli>\u003Cstrong>Named over global\u003C\u002Fstrong> unless the rule truly applies to almost all routes.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>SSR-safe session source\u003C\u002Fstrong> (cookies \u002F server-aware auth), not only \u003Ccode>localStorage\u003C\u002Fcode>.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Always \u003Ccode>return navigateTo(...)\u003C\u002Fcode>\u003C\u002Fstrong> so Nuxt waits on the redirect.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Keep middleware pure and short\u003C\u002Fstrong> — no heavy data fetching; fetch in the page with \u003Ccode>useAsyncData\u003C\u002Fcode>\u002F\u003Ccode>useFetch\u003C\u002Fcode>.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Protect APIs separately\u003C\u002Fstrong> — middleware is necessary but not sufficient for security.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Log decisions in development\u003C\u002Fstrong> — path, user present?, redirect target.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Align with lifecycle knowledge\u003C\u002Fstrong> — gates early, DOM work in \u003Ccode>onMounted\u003C\u002Fcode> (see lifecycle guide).\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>Common Mistakes\u003C\u002Fh2>\n\u003Cul>\n  \u003Cli>\u003Cstrong>Using \u003Ccode>localStorage\u003C\u002Fcode> as the only auth check\u003C\u002Fstrong> → Fix: cookie\u002Fsession that exists on SSR, or accept client-only apps and live with first-paint limits.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Calling \u003Ccode>navigateTo\u003C\u002Fcode> without \u003Ccode>return\u003C\u002Fcode>\u003C\u002Fstrong> → Fix: \u003Ccode>return navigateTo(...)\u003C\u002Fcode>.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Putting secrets or DB logic in route middleware\u003C\u002Fstrong> → Fix: call a server API \u002F use server routes; keep client-safe decisions in middleware.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Auth only in \u003Ccode>onMounted\u003C\u002Fcode>\u003C\u002Fstrong> → Fix: move the gate to middleware to avoid UI flash.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>One giant \u003Ccode>.global.ts\u003C\u002Fcode> for everything\u003C\u002Fstrong> → Fix: split named middlewares; attach per page\u002Flayout.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Confusing \u003Ccode>server\u002Fmiddleware\u003C\u002Fcode> with route middleware\u003C\u002Fstrong> → Fix: use route middleware for page guards; server middleware for HTTP-level concerns.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Assuming middleware never runs on the server\u003C\u002Fstrong> → Fix: write isomorphic, environment-aware code.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>Frequently Asked Questions\u003C\u002Fh2>\n\n\u003Ch3>What is Nuxt middleware?\u003C\u002Fh3>\n\u003Cp>It is a function that runs before a route navigation completes. You use it to allow the page, redirect the user, or abort the navigation — commonly for authentication and access control.\u003C\u002Fp>\n\n\u003Ch3>How do I add auth middleware in Nuxt?\u003C\u002Fh3>\n\u003Cp>Create \u003Ccode>middleware\u002Fauth.ts\u003C\u002Fcode> with \u003Ccode>defineNuxtRouteMiddleware\u003C\u002Fcode>, redirect when there is no session, then set \u003Ccode>definePageMeta({ middleware: 'auth' })\u003C\u002Fcode> on protected pages — or use \u003Ccode>auth.global.ts\u003C\u002Fcode> if almost every route needs it.\u003C\u002Fp>\n\n\u003Ch3>Nuxt middleware vs Vue Router navigation guards?\u003C\u002Fh3>\n\u003Cp>Conceptually similar (run before entering a route). Nuxt wraps this with file-based middleware, \u003Ccode>definePageMeta\u003C\u002Fcode>, SSR execution on first load, and helpers like \u003Ccode>navigateTo\u003C\u002Fcode>. You usually write Nuxt middleware instead of hand-wiring Vue Router guards.\u003C\u002Fp>\n\n\u003Ch3>Is Nuxt middleware worth it?\u003C\u002Fh3>\n\u003Cp>Yes, whenever you have protected routes, onboarding steps, or locale\u002Frole gates. It prevents UI flash, centralizes rules, and fits SSR. For a public-only brochure site with zero gated pages, you may not need it.\u003C\u002Fp>\n\n\u003Ch3>Does Nuxt middleware run on the server?\u003C\u002Fh3>\n\u003Cp>It can — especially on the first request with SSR enabled. Later client-side navigations run it in the browser. Write middleware that works in both places unless you intentionally mark client-only behavior.\u003C\u002Fp>\n\n\u003Ch3>Route middleware vs server middleware in Nuxt?\u003C\u002Fh3>\n\u003Cp>Route middleware guards pages during navigation. Server middleware in \u003Ccode>server\u002Fmiddleware\u003C\u002Fcode> runs on Nitro HTTP requests. Use both when needed, but don’t mix their jobs.\u003C\u002Fp>\n\n\u003Ch2>Summary\u003C\u002Fh2>\n\u003Cp>Nuxt middleware is your route checkpoint: it decides who may enter a page before the UI settles. Master named vs global, SSR-safe session checks, and correct \u003Ccode>navigateTo\u003C\u002Fcode>\u002F\u003Ccode>abortNavigation\u003C\u002Fcode> usage, and auth UX becomes predictable.\u003C\u002Fp>\n\u003Cp>Keep middleware thin, pages focused on content, and APIs properly protected. That split matches how Nuxt’s navigation and lifecycle are designed to work together.\u003C\u002Fp>\n\u003Cp>Next step: add one named \u003Ccode>auth\u003C\u002Fcode> middleware, protect a single admin page, and test both hard refresh and in-app navigation. Then expand with roles via \u003Ccode>to.meta\u003C\u002Fcode>.\u003C\u002Fp>\n\n\u003Ch2>Key Takeaways\u003C\u002Fh2>\n\u003Cul>\n  \u003Cli>Middleware runs before the page navigation completes — ideal for auth and redirects.\u003C\u002Fli>\n  \u003Cli>Use named middleware by default; reserve \u003Ccode>.global\u003C\u002Fcode> for truly app-wide rules.\u003C\u002Fli>\n  \u003Cli>First load may run on the server — avoid browser-only APIs without guards.\u003C\u002Fli>\n  \u003Cli>Always \u003Ccode>return navigateTo(...)\u003C\u002Fcode>; don’t treat middleware as full API security.\u003C\u002Fli>\n  \u003Cli>Pair this with the \u003Ca href=\"\u002Fblog\u002Fnuxt-lifecycle-explained\">Nuxt lifecycle\u003C\u002Fa> mental model: gates early, DOM later.\u003C\u002Fli>\n\u003C\u002Ful>","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785902953511-osy6pt.webp","Nuxt Middleware Explained — Route Guards & Auth","Learn Nuxt middleware in depth: global vs named, SSR-safe auth, redirects, order of execution, and real examples. Clear steps + FAQs.","",[19,20,21,22,23],"Nuxt","Middleware","SSR","Auth","Vue","published","2026-08-05T04:09:38.347+00:00",18,null,"2026-08-05T04:09:19.126745+00:00","2026-08-05T04:09:38.496803+00:00",{"variant":31,"profile":36,"heroStats":49,"aboutParagraphs":53,"aboutPillars":60,"aboutFacts":73,"skillCategories":86,"experiences":129,"education":156,"projects":175,"languages":245,"interests":248},{"id":32,"slug":33,"label":34,"is_active":35,"sort_order":4},"481b2725-e0f6-43df-beea-937ec806a438","full-stack-developer","Full Stack Developer",true,{"name":37,"title":38,"tagline":38,"photo_url":39,"summary":40,"email":41,"phone":17,"location":42,"linkedin":43,"github":44,"instagram":45,"hero_headline":46,"hero_headline_accent":47,"hero_subheadline":48},"Mohd Anish","Full Stack Developer ","\u002Fprofile.png","Full Stack Developer with 3.5+ years of experience specializing in Laravel, Vue.js, Nuxt.js, MySQL, and modern web technologies. Experienced in designing, developing, and maintaining scalable web applications with a strong focus on performance, security, and code quality.","anhali736@gmail.com","Rajasthan, India","linkedin.com\u002Fin\u002Fmohd-anish-23096635a","https:\u002F\u002Fgithub.com\u002Fmrmolani76","https:\u002F\u002Fwww.instagram.com\u002Fmohdanish.me\u002F","Building Scalable Web Apps","using Modern Technologies","Building secure, scalable, and high-performance web applications using Laravel, Vue.js, Nuxt.js, and MySQL.",[50],{"value":51,"label":52},"3.5+","Yrs Development",[54,56,58],{"html":55},"I'm a \u003Cspan class=\"text-gold font-medium\">Full Stack Developer\u003C\u002Fspan> passionate about building secure, scalable, and high-performance web applications. I enjoy solving complex problems and creating modern digital experiences with clean, maintainable code.",{"html":57},"I specialize in \u003Cspan class=\"text-gold font-medium\">Laravel\u003C\u002Fspan>, \u003Cspan class=\"text-foreground\">Vue.js\u003C\u002Fspan>, \u003Cspan class=\"text-foreground\">Nuxt.js\u003C\u002Fspan>, \u003Cspan class=\"text-foreground\">MySQL\u003C\u002Fspan>, and \u003Cspan class=\"text-foreground\">REST APIs\u003C\u002Fspan>, building responsive and scalable applications with a strong focus on performance, security, and code quality.",{"html":59},"With \u003Cspan class=\"text-foreground\">3.5+ years of experience\u003C\u002Fspan>, I've contributed to enterprise-grade applications, including compliance-critical modules for the \u003Cspan class=\"text-foreground\">Complere eQMS\u003C\u002Fspan> platform. I'm committed to continuous learning and building software that is reliable, maintainable, and ready for real-world use.",[61,65,69],{"icon":62,"label":63,"description":64},"lucide:code-2","Build","Scalable, clean web apps",{"icon":66,"label":67,"description":68},"lucide:trending-up","Grow","Marketing-driven results",{"icon":70,"label":71,"description":72},"lucide:shield-check","Ship","Reliable, compliant systems",[74,78,82],{"icon":75,"label":76,"value":77},"lucide:settings","Core Stack","Laravel · Nuxt · Vue · MySQL",{"icon":79,"label":80,"value":81},"lucide:building-2","Currently","Complibued — eQMS Platform",{"icon":83,"label":84,"value":85},"lucide:map-pin","Availability","Open to opportunities",[87,102,113,124],{"title":88,"icon":89,"color":90,"show_on_home":35,"show_on_resume":35,"skills":91},"Backend Development","lucide:database","from-gold-soft to-gold-deep",[92,93,94,95,96,97,98,99,100,101],"Laravel","PHP","Supabase (BaaS)","MySQL","REST APIs","Git","Docker","Redis","GitHub Actions","Cloudflare",{"title":103,"icon":104,"color":90,"show_on_home":35,"show_on_resume":105,"skills":106},"Frontend Development","lucide:code",false,[107,108,109,110,111,112],"Nuxt.js","Vue.js","React","TypeScript","Tailwind CSS","JavaScript",{"title":114,"icon":115,"color":90,"show_on_home":35,"show_on_resume":105,"skills":116},"AI & Automation","lucide:zap",[117,118,119,120,121,122,123],"Prompt Engineering","ChatGPT & Claude","Google Gemini","AI Grok","GitHub Copilot","AI Content Strategy","Workflow Automation",{"title":125,"icon":126,"color":90,"show_on_home":35,"show_on_resume":35,"skills":127},"Development","lucide:wrench",[92,93,108,107,112,110,111,96,95,128],"Git & GitHub",[130],{"role":34,"company":131,"note":132,"period":133,"description":134,"stack":135,"color":90,"icon":136,"points":137},"Complibued","Complere eQMS — Pharmaceutical SaaS","2023 – Present","Building Complere eQMS, a cloud-based Quality Management System for regulated life sciences using Laravel and Nuxt.js. Developed compliance-critical modules — Document Control, LMS, Events, CAPA, Change Control, Audit, and Risk Assessment.","Laravel · Vue\u002FNuxt · MySQL · Tailwind CSS","lucide:folder-git-2",[138,141,143,145,147,150,152,154],{"text":139,"surface":140},"Developing and maintaining a pharma-focused eQMS platform using Laravel and Nuxt.js.","resume",{"text":142,"surface":140},"Built compliance-critical modules: Document Control, Training (LMS), Event Handling, CAPA, Change Control (CR), Audit, and Risk Assessment (RA).",{"text":144,"surface":140},"Implemented approval workflows, version control, and immutable audit trails aligned to 21 CFR Part 11.",{"text":146,"surface":140},"Collaborated with QA teams to meet pharmaceutical compliance standards.",{"text":148,"surface":149},"Built Document Control & LMS (training) modules","home",{"text":151,"surface":149},"Implemented CAPA and Event management workflows",{"text":153,"surface":149},"Developed Change Control (CR) with impact-assessed approvals",{"text":155,"surface":149},"Delivered Audit & Risk Assessment (RA) modules with audit trails",[157,162,166,171],{"degree":158,"school":159,"period":160,"score":161},"M.Sc. (Computer Science)","MDS University, Ajmer","2023 – 2025","73%",{"degree":163,"school":159,"period":164,"score":165},"BCA","2020 – 2023","71%",{"degree":167,"school":168,"period":169,"score":170},"Senior Secondary (12th)","RBSE, Ajmer","2018 – 2019","68.80%",{"degree":172,"school":168,"period":173,"score":174},"Secondary (10th)","2016 – 2017","48.75%",[176,193,210],{"title":177,"slug":178,"description":179,"why":180,"category":181,"image":182,"emoji":183,"link":184,"is_active":35,"stack":185,"features":187,"metrics":192},"Inventory Manager","inventory-manager","Professional inventory management system for tracking stock, orders, and enterprise operations. Powered by Supabase auth and a relational MySQL backend.","Stock and order tracking needed a reliable source of truth for enterprise operations. This system was built so teams can monitor inventory, manage orders, and report status from one authenticated app.","Enterprise","bg-gradient-to-br from-gold-soft\u002F15 via-gold\u002F5 to-transparent","📦","https:\u002F\u002Fruby-enterprise.vercel.app\u002F",[108,186,95,111,110],"Supabase",[188,189,190,191],"Stock Tracking","Order Management","User Authentication","Reporting & Analytics",[],{"title":194,"slug":195,"description":196,"why":197,"category":198,"image":199,"emoji":200,"link":201,"is_active":35,"stack":202,"features":204,"metrics":209},"Random Video Chat","random-video-chat","Omegle-style platform for spontaneous 1-on-1 video conversations with strangers. Uses WebRTC for peer-to-peer video and Supabase Realtime for matchmaking and signaling.","I wanted to explore real-time peer connections without a heavy media server. The app was built to practice WebRTC + realtime matchmaking and deliver instant 1-on-1 video chat with no account friction.","Real-time","bg-gradient-to-br from-gold\u002F15 via-gold\u002F5 to-transparent","🎥","https:\u002F\u002Fomegle-seven-xi.vercel.app\u002F",[108,203,186,111,110],"WebRTC",[205,206,207,208],"Peer-to-Peer Video","Random Matchmaking","Realtime Signaling","No Sign-up Required",[],{"title":211,"slug":212,"description":213,"why":214,"category":215,"image":199,"emoji":216,"link":217,"is_active":35,"stack":218,"features":226,"metrics":235},"Nexro","nexro","Multi-tenant retail web app for GST billing and inventory — products, purchases, sales, POS, quotations, supplier ledgers, and reports. Landing page: nexro.me.","Retail shops were juggling billing, stock, purchases, and supplier dues across sheets and separate tools. Nexro was built as a multi-tenant SaaS so each shop gets its own data on a shared Laravel + Nuxt stack, with GST invoices, live stock, and day-to-day ops from one login.","Web App \u002F SaaS","🏪","https:\u002F\u002Fnexro.me",[219,220,221,222,111,110,95,223,224,225,98],"Laravel 12","Nuxt 4","Vue 3","Vuetify 3","stancl\u002Ftenancy","Laravel Sanctum","Spatie Permission",[227,228,229,230,231,232,233,234],"Multi-tenant shop isolation","GST billing & POS","Inventory with SKU \u002F barcode \u002F serial","Purchases & supplier ledger","Quotations → invoice","Sales, stock & dues reports","Thermal & A4 print","Region-aware landing (nexro.me)",[236,239,242],{"value":237,"label":238},"1","Product platform",{"value":240,"label":241},"7+","Core modules",{"value":243,"label":244},"MT","Multi-tenant",[246,247],"Hindi","English",[249,250,251],"Web Development","Video Content","New Tools & Tech",[],[254,269,286,301,313,327,339,351,364,377,387,398,410,422,436,438,448,457,468,481,493,502,513,526],{"id":255,"title":256,"slug":257,"excerpt":258,"cover_image":259,"tags":260,"published_at":266,"updated_at":267,"view_count":268},"1fac09f2-990e-4ebf-99b1-0cc532e7cb08","Soft Delete Inventory Bug — Phantom Serial Stock After Purchase Delete","soft-delete-inventory-bug-phantom-serial-stock-after-purchase-delete","Soft-deleting a purchase looked fine until serial-tracked products stayed sellable. The movement ran, quantity didn’t move, and serials were never detached.","https:\u002F\u002Fik.imagekit.io\u002F93se7t7h4e\u002Fportfolio\u002Fposts\u002Fblog\u002Fcovers\u002F1793165769172-Phantom-Inventory_-Deleted-Warehouse-Order_Z0BIZdhyJ.webp",[261,262,263,264,265,6],"laravel","inventory","soft-delete","serial-numbers","stock-movements","2026-10-28T05:36:31.148+00:00","2026-10-28T05:36:32.188948+00:00",21,{"id":270,"title":271,"slug":272,"excerpt":273,"cover_image":274,"tags":275,"published_at":283,"updated_at":284,"view_count":285},"b2a6b718-c6e5-42fa-9358-22e84035aaf2","Multi-Tenant Inventory Manager with Nuxt 3 and Supabase","multi-tenant-inventory-manager-nuxt-supabase","A shop-billing SaaS on Nuxt 3 and Supabase: stock, invoices, UPI links, AI bill scan, and per-shop storefronts — with RLS so shop_id is never trusted from the client.","https:\u002F\u002Fik.imagekit.io\u002F93se7t7h4e\u002Fportfolio\u002Fposts\u002Flibrary\u002F1792583563566-Modern-Retail-POS-Dashboard-Network_-BFGj_TT0.webp?updatedAt=1792583565092",[276,277,278,262,6,279,280,281,282],"nuxt","supabase","multi-tenancy","vue","pinia","vuetify","ai","2026-10-21T12:07:58.857+00:00","2026-10-21T12:07:59.070373+00:00",16,{"id":287,"title":288,"slug":289,"excerpt":290,"cover_image":291,"tags":292,"published_at":298,"updated_at":299,"view_count":300},"58f0adc6-f4e9-4501-bc0e-ab83cc2cc073","Laravel Sanctum 419 Fix — Why XSRF-TOKEN Must Stay Encrypted","laravel-sanctum-419-xsrf-token-encryption","Sanctum SPA login kept returning 419 CSRF token mismatch. The bug wasn’t domains or cookies “not sticking” — it was excluding XSRF-TOKEN from EncryptCookies while Laravel decrypts the X-XSRF-TOKEN header.","https:\u002F\u002Fik.imagekit.io\u002F93se7t7h4e\u002Fportfolio\u002Fposts\u002Fblog\u002Fcovers\u002F1792229994752-From-CSRF-Error-to-Secure-Fix_FIVIW5po2.webp",[92,293,294,295,296,19,297],"Sanctum","CSRF","419","SPA","API Authentication","2026-10-17T09:40:04.212+00:00","2026-10-17T09:40:06.051151+00:00",17,{"id":302,"title":303,"slug":304,"excerpt":305,"cover_image":306,"tags":307,"published_at":310,"updated_at":311,"view_count":312},"7b4bee90-b35b-4ced-ae8c-0a71e7d968fb","ImageKit Nuxt Upload — Keep Private Keys Off the Client","imagekit-nuxt-upload-secure","ImageKit Nuxt upload means the browser never sees your private key. Sign or upload on the server, return a CDN URL, and store that URL in your CMS or database.","https:\u002F\u002Fik.imagekit.io\u002F93se7t7h4e\u002Fportfolio\u002Fposts\u002Fblog\u002Fcovers\u002F1792216420019-Secure-Upload-Architecture-Flow_MGyvtL5tR.webp",[19,308,23,110,309],"ImageKit","SEO","2026-10-17T05:55:24.556+00:00","2026-10-17T05:55:24.735773+00:00",23,{"id":314,"title":315,"slug":316,"excerpt":317,"cover_image":318,"tags":319,"published_at":325,"updated_at":326,"view_count":285},"bd55b3c6-8bd3-447d-99ad-d46a97490d7b","Apache 2 Installation on Ubuntu: Step-by-Step","apache-2-installation-ubuntu","Install Apache 2 on Ubuntu with apt, start the service, open the firewall, and verify the default page. Part 2 of the Apache 2 series — clean setup before virtual hosts.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1788925690969-7zm2c2.webp",[320,321,322,323,324],"Apache","Ubuntu","Installation","Linux","Web Server","2026-09-09T03:49:25.809+00:00","2026-09-09T03:49:26.679843+00:00",{"id":328,"title":329,"slug":330,"excerpt":331,"cover_image":332,"tags":333,"published_at":336,"updated_at":337,"view_count":338},"8c75a723-b1a7-4fab-9bb9-71a111c9d4f8","Apache vs Nginx: What They Are and When to Use Each","apache-vs-nginx","Apache and Nginx are web servers. They take HTTP requests and return files or pass work to PHP, Node, or another app. Apache fits shared hosting and .htaccess; Nginx is the usual reverse proxy on an Ubuntu VPS.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1788524039845-wrez6s.webp",[320,334,321,324,323,335],"Nginx","DevOps","2026-09-04T12:14:08.218+00:00","2026-09-04T12:14:08.430018+00:00",9,{"id":340,"title":341,"slug":342,"excerpt":343,"cover_image":344,"tags":345,"published_at":348,"updated_at":349,"view_count":350},"40dd3304-99d2-4948-b8c1-44625f1f4306","What Is a Virtual Host? Host Multiple Sites on One Ubuntu VPS","virtual-host-linux-multiple-websites","A virtual host maps each domain to its own folder on one server. Developers use this on Ubuntu VPSes so portfolio, API, and staging share one bill. Same idea on any Linux — Ubuntu is just what most tutorials and clouds default to.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1788523755345-javhet.webp",[346,321,334,323,347,335],"Virtual Host","VPS","2026-09-04T12:09:22.623+00:00","2026-09-04T12:09:22.931401+00:00",12,{"id":352,"title":353,"slug":354,"excerpt":355,"cover_image":356,"tags":357,"published_at":361,"updated_at":362,"view_count":363},"6e45f39b-1ade-47f0-a0b0-b4cd386a10dc","Laravel Queues & Jobs: How Background Processing Works","laravel-queues-and-jobs","Laravel queues move slow work off the HTTP request. You push a Job onto a queue, a worker runs it later, and the user gets a fast response. Use them for mail, webhooks, image work, and anything that can fail and retry.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1787286979145-0i7ewp.webp",[92,358,359,93,360],"Queues","Jobs","backend","2026-08-21T04:36:56.222+00:00","2026-08-21T04:36:56.606735+00:00",20,{"id":365,"title":366,"slug":367,"excerpt":368,"cover_image":369,"tags":370,"published_at":374,"updated_at":375,"view_count":376},"938c7bd9-2cf3-4a81-8dae-cf88c09e64ca","Laravel N+1 Query Problem: How to Detect and Fix It","laravel-n-plus-1-query-problem","The Laravel N+1 query problem is when one listing query is followed by one extra query per row. You spot it in Telescope or the query log, then fix it with with(), withCount(), and nested eager loads.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1787199419649-niq9k8.webp",[92,371,372,373,93],"Eloquent","N+1","performance","2026-08-20T04:17:43.609+00:00","2026-08-20T05:50:24.297698+00:00",14,{"id":378,"title":379,"slug":380,"excerpt":381,"cover_image":382,"tags":383,"published_at":385,"updated_at":386,"view_count":26},"76717847-4080-4ae6-a2d8-b35badc46be3","Laravel Eloquent Relationships","laravel-eloquent-relationships","Laravel Eloquent relationships map how models connect — hasMany, belongsTo, belongsToMany, and more. Define them once, then load related rows with with() instead of stuffing joins into every query.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1787122982331-16979e.webp",[92,371,93,384,360],"ORM","2026-08-19T07:03:17.721+00:00","2026-08-20T04:19:08.829027+00:00",{"id":388,"title":389,"slug":390,"excerpt":391,"cover_image":392,"tags":393,"published_at":396,"updated_at":397,"view_count":285},"6bbe0ad8-0c6d-4172-b279-ded8e2ca9416","Laravel Database Transactions: When and Why to Use DB::transaction()","laravel-database-transactions","DB::transaction() runs a closure inside a SQL transaction: Laravel commits if it finishes, and rolls back if it throws. Use it when one action writes more than one row and a half-finished write would leave bad data.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1787114417893-hp3hmc.webp",[92,394,371,93,395],"Database","Transactions","2026-08-19T04:44:00.327+00:00","2026-08-19T05:14:18.190197+00:00",{"id":399,"title":400,"slug":401,"excerpt":402,"cover_image":403,"tags":404,"published_at":408,"updated_at":409,"view_count":376},"d1020b7b-b410-414f-9ceb-eb0501bc905e","Laravel Auditing Package — Track Model Changes the Right Way","laravel-auditing-package","The Laravel auditing package records old and new model values, the user who changed them, and when it happened—without you inventing a second history table for every feature.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1786778101029-mwb9sf.webp",[92,405,93,406,407],"Auditing","Security","Activity Log","2026-08-15T21:24:32.135+00:00","2026-08-15T21:24:32.194447+00:00",{"id":411,"title":412,"slug":413,"excerpt":414,"cover_image":415,"tags":416,"published_at":419,"updated_at":420,"view_count":421},"3d5eb867-6288-48c4-af04-8b7ece8b874e","Laravel Lifecycle — How a Request Becomes a Response","laravel-lifecycle","The Laravel lifecycle is the path from HTTP request to response: bootstrap, service providers, middleware, routing, then the controller. Know that path and most “random” bugs stop being random.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1786777544862-khxf92.webp",[92,93,417,20,418],"Request Lifecycle","Backend","2026-08-15T07:15:13.877+00:00","2026-08-15T07:15:13.978037+00:00",11,{"id":423,"title":424,"slug":425,"excerpt":426,"cover_image":427,"tags":428,"published_at":434,"updated_at":435,"view_count":376},"2ab5e08a-7117-43c5-87eb-0789a2fd3af4","Claude Code Best Practices for Large Codebases — Scope Before You Ship","claude-code-best-practices-large-codebases","On a big repo, Claude Code only helps if you lock rules in CLAUDE.md, scope every ticket, plan multi-file edits, and review the diff like a PR.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1786178453897-dulbmv.webp",[429,430,431,432,433],"claude-code","ai-coding","large-codebases","monorepo","developer-tools","2026-08-08T08:41:03.571+00:00","2026-08-08T08:41:03.839922+00:00",{"id":9,"title":10,"slug":11,"excerpt":12,"cover_image":14,"tags":437,"published_at":25,"updated_at":29,"view_count":26},[19,20,21,22,23],{"id":439,"title":440,"slug":441,"excerpt":442,"cover_image":443,"tags":444,"published_at":446,"updated_at":447,"view_count":350},"e0d9941b-467d-45cc-bf12-45390cf9aeaa","Nuxt Lifecycle Explained — Server, Client & Hooks Made Simple","nuxt-lifecycle-explained","Nuxt lifecycle is the order your app boots, fetches data, renders HTML on the server, hydrates in the browser, then runs page navigation — so you know where to put code safely.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785901639981-9tgcl5.webp",[19,23,21,445,112],"Lifecycle","2026-08-05T03:54:08.301+00:00","2026-08-05T03:54:08.919676+00:00",{"id":449,"title":450,"slug":451,"excerpt":452,"cover_image":453,"tags":454,"published_at":455,"updated_at":456,"view_count":312},"23c9cf92-232b-460f-9825-a9c53e350600","How to Use Laravel Sanctum for API Authentication — SPA Cookies & Tokens","laravel-api-authentication","Laravel Sanctum authenticates first-party SPAs with secure cookies and issues API tokens for mobile or third-party clients—without the complexity of full OAuth.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785833713437-wcqb6c.webp",[92,293,297,93,296,406],"2026-08-04T08:56:17.304+00:00","2026-08-06T04:07:09.059636+00:00",{"id":458,"title":459,"slug":460,"excerpt":461,"cover_image":462,"tags":463,"published_at":466,"updated_at":467,"view_count":26},"f50b774a-c745-41aa-a3b0-72ac1f5b7117","Laravel Sanctum vs Passport — Which API Auth Should You Use?","laravel-sanctum-vs-passport","Laravel Sanctum is the lighter choice for SPAs and simple API tokens; Passport is full OAuth2 for third-party apps. Pick Sanctum for most apps, Passport when you need real OAuth2.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785817155174-054d6s.webp",[92,293,464,297,93,465,296],"Passport","OAuth2","2026-08-04T04:19:37.286+00:00","2026-08-04T04:49:08.25034+00:00",{"id":469,"title":470,"slug":471,"excerpt":472,"cover_image":473,"tags":474,"published_at":478,"updated_at":479,"view_count":480},"ef36ca16-73ab-4f9a-9584-ff70a60da5f5","Laravel vs NestJS in 2026: Which Backend Should US Startups Choose?","laravel-vs-nestjs-2026-us-startups","Laravel vs NestJS for US startups in 2026: compare speed, TypeScript, hiring, SaaS MVPs, and real-time apps — and pick the backend that matches your team.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785609396341-ungcby.jpg",[92,475,418,476,477,93,110,249],"NestJS","SaaS","Startups","2026-08-01T18:40:05.071+00:00","2026-08-01T18:40:05.261242+00:00",38,{"id":482,"title":483,"slug":484,"excerpt":485,"cover_image":486,"tags":487,"published_at":491,"updated_at":492,"view_count":350},"c4e41758-834c-476e-8830-f776c963a784","What Is TypeScript? A Beginner’s Guide to Safer JavaScript","what-is-typescript","TypeScript is JavaScript with types. Learn what it is, how it works, and how to write your first typed script with clear examples and FAQs.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785574204088-8bc8es.jpg",[110,112,249,488,489,490],"Programming","Beginners","Frontend","2026-08-01T08:50:45.861+00:00","2026-08-01T08:50:45.958378+00:00",{"id":494,"title":495,"slug":496,"excerpt":497,"cover_image":498,"tags":499,"published_at":500,"updated_at":501,"view_count":376},"37ee32f1-7b8d-4c4d-92b4-37bb37ff64c5","What Is JavaScript? A Beginner’s Guide to Modern Web Development","what-is-javascript","JavaScript is the programming language that makes websites interactive. Learn what it is, how it works, and how to write your first script with clear examples and FAQs.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785561346515-utrr91.jpg",[112,249,488,489,490],"2026-08-01T05:16:12.728+00:00","2026-08-01T08:50:11.164531+00:00",{"id":503,"title":504,"slug":505,"excerpt":506,"cover_image":507,"tags":508,"published_at":511,"updated_at":512,"view_count":26},"f238da13-8416-41e6-8281-a6185efd4bd4","Laravel Sanctum Explained: Simple API Authentication for Modern Apps","laravel-sanctum-api-authentication","Laravel Sanctum makes API authentication simple — whether you need token-based APIs for mobile apps or cookie-based auth for SPAs. Here’s how it works, without the jargon.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785470074981-vejfi4.jpg",[92,293,509,510,296],"API","Authentication","2026-08-01T04:13:15.178+00:00","2026-08-01T08:50:11.393519+00:00",{"id":514,"title":515,"slug":516,"excerpt":517,"cover_image":518,"tags":519,"published_at":523,"updated_at":524,"view_count":525},"d8c77913-46f4-4012-ade6-bd5a81676001","Laravel Module Structure Explained: Keep Large Apps Clean","laravel-module-structure-explained","A practical guide to Laravel module architecture — folder layout, providers, routes, and boundaries that keep features independent as your app grows.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785385385865-8oyk12.png",[92,93,520,521,418,522],"Modules","Architecture","Clean Code","2026-07-30T04:54:17.431+00:00","2026-08-01T08:50:11.599795+00:00",6,{"id":527,"title":528,"slug":529,"excerpt":530,"cover_image":531,"tags":532,"published_at":539,"updated_at":540,"view_count":363},"26ccd19c-a8bb-419d-be11-efd1d221b415","Cursor vs Claude vs ChatGPT: Which AI Actually Helps with Laravel & Nuxt?","cursor-ai-vs-claude-code-vs-chatgpt-for-laravel-nuxt-development-2026","Tired of constantly copying and pasting code between your Vue frontend and PHP backend? I tested Cursor, Claude Code, and ChatGPT to see which one actually speeds up a real-world Laravel and Nuxt workflow. Here is my breakdown.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785300697566-pn766r.png",[92,533,534,535,536,537,538],"Nuxt 3","AI for Developers","Cursor","Claude Code","ChatGPT","Full Stack","2026-07-29T04:46:50.88+00:00","2026-08-01T08:50:11.809909+00:00"]