[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"site-settings":3,"blog-post:nuxt-lifecycle-explained":8,"blog-posts-latest:24":30,"site-content":323,"blog-comments:e0d9941b-467d-45cc-bf12-45390cf9aeaa":540},{"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},"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.","\u003Ch2>Quick Answer\u003C\u002Fh2>\n\u003Cp>The Nuxt lifecycle is the ordered path your app takes from start to screen: boot config and plugins, run middleware, fetch data, render HTML (often on the server), send it to the browser, “hydrate” so Vue becomes interactive, then handle route changes. Knowing this order stops bugs like using \u003Ccode>window\u003C\u002Fcode> too early or fetching data in the wrong place.\u003C\u002Fp>\n\n\u003Ch2>Quick Facts\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Topic:\u003C\u002Fstrong> Nuxt lifecycle (SSR, hydration, hooks)\u003Cbr>\n\u003Cstrong>Category:\u003C\u002Fstrong> Nuxt.js \u002F Frontend Framework\u003C\u002Fp>\n\n\u003Ch2>Table of Contents\u003C\u002Fh2>\n\u003Cul>\n  \u003Cli>What Is the Nuxt Lifecycle?\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 the Nuxt Lifecycle?\u003C\u002Fh2>\n\u003Cp>Think of Nuxt like a restaurant kitchen with two rooms: a \u003Cstrong>server kitchen\u003C\u002Fstrong> (prepares the first HTML plate) and a \u003Cstrong>browser dining room\u003C\u002Fstrong> (makes the page live and clickable).\u003C\u002Fp>\n\u003Cp>“Lifecycle” simply means \u003Cem>what happens in which order\u003C\u002Fem> — plugins load, middleware checks the visitor, data loads, the page paints, then user clicks move to the next page. Vue component hooks (\u003Ccode>onMounted\u003C\u002Fcode>, etc.) are part of this story, but Nuxt also adds its own app-level stages for SSR and routing.\u003C\u002Fp>\n\n\u003Ch2>Why It Matters\u003C\u002Fh2>\n\u003Cul>\n  \u003Cli>\u003Cstrong>Fewer production bugs\u003C\u002Fstrong> — you stop calling browser-only APIs during server render.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Faster perceived load\u003C\u002Fstrong> — first paint can use real HTML from the server instead of a blank spinner.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Correct data fetching\u003C\u002Fstrong> — \u003Ccode>useFetch\u003C\u002Fcode> \u002F \u003Ccode>useAsyncData\u003C\u002Fcode> line up with SSR so SEO and share previews get real content.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Cleaner architecture\u003C\u002Fstrong> — auth checks, analytics, and UI setup each have a clear home (middleware, plugins, or client hooks).\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>How It Works\u003C\u002Fh2>\n\u003Cp>In one sentence: Nuxt boots the app, resolves the route, loads data, renders, then hands control to the browser.\u003C\u002Fp>\n\u003Col>\n  \u003Cli>\u003Cstrong>Boot\u003C\u002Fstrong> — Nuxt config, modules, and plugins start (server plugins first on SSR).\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Route + middleware\u003C\u002Fstrong> — Nuxt matches the URL and runs route middleware (global, then layout\u002Fpage).\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Data\u003C\u002Fstrong> — composables like \u003Ccode>useAsyncData\u003C\u002Fcode> \u002F \u003Ccode>useFetch\u003C\u002Fcode> run so the page has payload before (or while) render.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Render\u003C\u002Fstrong> — Vue renders the page tree to HTML on the server (SSR) or to DOM on the client (SPA\u002FCSR).\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Ship + hydrate\u003C\u002Fstrong> — browser gets HTML + payload, Vue attaches event listeners so the page becomes interactive.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Navigate\u003C\u002Fstrong> — client-side route changes reuse the living Vue app; middleware and data can run again without a full reload.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Simple map:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Request → Nuxt app → Plugins → Middleware → Page data → Render HTML\n→ Browser receives HTML → Hydration → Interactive app → Client navigations\n\u003C\u002Fcode>\u003C\u002Fpre>\n\n\u003Ch2>Step-by-Step Guide\u003C\u002Fh2>\n\n\u003Ch3>Step 1: Know “where” your code runs\u003C\u002Fh3>\n\u003Cp>Ask one question before writing code: \u003Cstrong>server, client, or both?\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n  \u003Cli>\u003Cstrong>Server only\u003C\u002Fstrong> — secrets, DB calls via server routes \u002F Nitro, serverside plugin logic.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Client only\u003C\u002Fstrong> — \u003Ccode>window\u003C\u002Fcode>, \u003Ccode>localStorage\u003C\u002Fcode>, analytics SDKs, DOM measurements.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Both\u003C\u002Fstrong> — shared UI state setup, many composables (be careful with browser APIs).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Use \u003Ccode>import.meta.server\u003C\u002Fcode> \u002F \u003Ccode>import.meta.client\u003C\u002Fcode> (or \u003Ccode>process.server\u003C\u002Fcode> \u002F \u003Ccode>process.client\u003C\u002Fcode> in older setups) when branching.\u003C\u002Fp>\n\n\u003Ch3>Step 2: Put “app-wide” setup in plugins\u003C\u002Fh3>\n\u003Cp>Plugins run early when the Nuxt app starts. Good for:\u003C\u002Fp>\n\u003Cul>\n  \u003Cli>Registering a library\u003C\u002Fli>\n  \u003Cli>Providing a helper via \u003Ccode>nuxtApp.provide\u003C\u002Fcode>\u003C\u002Fli>\n  \u003Cli>Running startup logic once\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Name client-only plugins with \u003Ccode>.client.ts\u003C\u002Fcode> and server-only with \u003Ccode>.server.ts\u003C\u002Fcode> so Nuxt loads them in the right room.\u003C\u002Fp>\n\n\u003Ch3>Step 3: Protect routes with middleware\u003C\u002Fh3>\n\u003Cp>Middleware runs \u003Cem>before\u003C\u002Fem> a page finishes navigating. Typical jobs:\u003C\u002Fp>\n\u003Cul>\n  \u003Cli>Redirect guests away from \u003Ccode>\u002Fadmin\u003C\u002Fcode>\u003C\u002Fli>\n  \u003Cli>Check auth token\u003C\u002Fli>\n  \u003Cli>Log or rewrite a path\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Remember: on first SSR request, middleware can run on the server too — so don’t assume \u003Ccode>window\u003C\u002Fcode> exists.\u003C\u002Fp>\n\n\u003Ch3>Step 4: Fetch page data the Nuxt way\u003C\u002Fh3>\n\u003Cp>Prefer \u003Ccode>useFetch\u003C\u002Fcode> or \u003Ccode>useAsyncData\u003C\u002Fcode> in pages\u002Fcomponents so Nuxt can:\u003C\u002Fp>\n\u003Cul>\n  \u003Cli>Fetch during SSR\u003C\u002Fli>\n  \u003Cli>Serialize the result into the payload\u003C\u002Fli>\n  \u003Cli>Reuse that payload on the client (no double fetch by default for the first paint)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Avoid putting critical first-paint content only inside \u003Ccode>onMounted\u003C\u002Fcode> — that runs \u003Cem>after\u003C\u002Fem> hydration, so crawlers and slow networks may see empty UI first.\u003C\u002Fp>\n\n\u003Ch3>Step 5: Use Vue component hooks at the right moment\u003C\u002Fh3>\n\u003Cp>Easy timing guide inside a page\u002Fcomponent:\u003C\u002Fp>\n\u003Cul>\n  \u003Cli>\u003Cstrong>\u003Ccode>setup\u003C\u002Fcode> \u002F script setup body\u003C\u002Fstrong> — runs early (can run on server during SSR).\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>\u003Ccode>onBeforeMount\u003C\u002Fcode>\u003C\u002Fstrong> — client-side, right before mount.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>\u003Ccode>onMounted\u003C\u002Fcode>\u003C\u002Fstrong> — DOM is ready; safe for charts, measuring elements, browser APIs.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>\u003Ccode>onBeforeUnmount\u003C\u002Fcode> \u002F \u003Ccode>onUnmounted\u003C\u002Fcode>\u003C\u002Fstrong> — clean timers, listeners, subscriptions.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Rule of thumb: \u003Cstrong>if it needs the real DOM or browser APIs, use \u003Ccode>onMounted\u003C\u002Fcode> (or a \u003Ccode>.client\u003C\u002Fcode> plugin).\u003C\u002Fstrong>\u003C\u002Fp>\n\n\u003Ch3>Step 6: Respect hydration\u003C\u002Fh3>\n\u003Cp>Hydration means Vue walks the server HTML and connects it to live state. If server HTML and client first render don’t match (different random IDs, \u003Ccode>Date.now()\u003C\u002Fcode>, \u003Ccode>window.innerWidth\u003C\u002Fcode> in template), you get hydration warnings\u002Fmismatches.\u003C\u002Fp>\n\u003Cp>Fix pattern: render a stable shared value first, then update client-only values after mount.\u003C\u002Fp>\n\n\u003Ch2>Real-World Example\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Goal:\u003C\u002Fstrong> A blog post page that should rank on Google and feel instant.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Bad flow:\u003C\u002Fstrong> Page mounts → \u003Ccode>onMounted\u003C\u002Fcode> fetches post → spinner for SEO bots and first users. Server HTML has almost no article text.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Better Nuxt flow:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n  \u003Cli>Visitor hits \u003Ccode>\u002Fblog\u002Fnuxt-lifecycle-explained\u003C\u002Fcode>.\u003C\u002Fli>\n  \u003Cli>Server runs middleware (optional redirect\u002Fchecks).\u003C\u002Fli>\n  \u003Cli>Page uses \u003Ccode>useAsyncData('post', () =&gt; $fetch('\u002Fapi\u002Fposts\u002F...'))\u003C\u002Fcode>.\u003C\u002Fli>\n  \u003Cli>Server renders real \u003Ccode>&lt;h1&gt;\u003C\u002Fcode> + article HTML.\u003C\u002Fli>\n  \u003Cli>Browser shows content immediately, then hydrates.\u003C\u002Fli>\n  \u003Cli>In \u003Ccode>onMounted\u003C\u002Fcode>, you optionally start a view counter or comments widget (client-only).\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Same page, different jobs: \u003Cem>content on the server path, decorations on the client path\u003C\u002Fem>.\u003C\u002Fp>\n\u003Cp>For a portfolio that already uses Nuxt + blog routes (like this site’s \u003Ca href=\"\u002Fblog\">blog\u003C\u002Fa>), this split is exactly how SEO-friendly posts stay fast and crawlable.\u003C\u002Fp>\n\n\u003Ch2>Pros &amp; Cons\u003C\u002Fh2>\n\u003Ch3>Advantages\u003C\u002Fh3>\n\u003Cul>\n  \u003Cli>Clear mental model for where code belongs\u003C\u002Fli>\n  \u003Cli>Better SEO and social previews via SSR HTML\u003C\u002Fli>\n  \u003Cli>Less duplicate fetching when payload is reused\u003C\u002Fli>\n  \u003Cli>Middleware + plugins keep auth and setup out of messy components\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Disadvantages\u003C\u002Fh3>\n\u003Cul>\n  \u003Cli>More concepts than a pure SPA (server vs client boundary)\u003C\u002Fli>\n  \u003Cli>Hydration mismatches take practice to spot and fix\u003C\u002Fli>\n  \u003Cli>Misplaced browser APIs cause “works on client, crashes on SSR” bugs\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>Best Practices\u003C\u002Fh2>\n\u003Cul>\n  \u003Cli>\u003Cstrong>Fetch for SEO in \u003Ccode>useAsyncData\u003C\u002Fcode>\u002F\u003Ccode>useFetch\u003C\u002Fcode>\u003C\u002Fstrong>, not only in \u003Ccode>onMounted\u003C\u002Fcode>.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Mark environments clearly\u003C\u002Fstrong> — \u003Ccode>.client\u003C\u002Fcode> \u002F \u003Ccode>.server\u003C\u002Fcode> plugins and \u003Ccode>ClientOnly\u003C\u002Fcode> when needed.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Keep secrets on the server\u003C\u002Fstrong> — never put API keys in client bundles.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Stable SSR output\u003C\u002Fstrong> — avoid random values and browser-only data in the first render.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Clean up on leave\u003C\u002Fstrong> — remove listeners\u002Ftimers in unmount hooks.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Middleware for gates, plugins for wiring, pages for UI + data\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>Common Mistakes\u003C\u002Fh2>\n\u003Cul>\n  \u003Cli>\u003Cstrong>Using \u003Ccode>window\u003C\u002Fcode> \u002F \u003Ccode>localStorage\u003C\u002Fcode> in setup during SSR\u003C\u002Fstrong> → Fix: move to \u003Ccode>onMounted\u003C\u002Fcode> or a \u003Ccode>.client\u003C\u002Fcode> plugin.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Fetching critical content only in \u003Ccode>onMounted\u003C\u002Fcode>\u003C\u002Fstrong> → Fix: use \u003Ccode>useFetch\u003C\u002Fcode>\u002F\u003Ccode>useAsyncData\u003C\u002Fcode> for first paint.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Hydration mismatch from \u003Ccode>new Date()\u003C\u002Fcode> or random IDs in template\u003C\u002Fstrong> → Fix: render after mount or use consistent server\u002Fclient values.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Auth checks only inside the page UI\u003C\u002Fstrong> → Fix: route middleware redirects early.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Assuming middleware is always browser-only\u003C\u002Fstrong> → Fix: write middleware that is SSR-safe.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Forgetting cleanup\u003C\u002Fstrong> → Fix: pair subscriptions with \u003Ccode>onUnmounted\u003C\u002Fcode>.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>Frequently Asked Questions\u003C\u002Fh2>\n\n\u003Ch3>What is the Nuxt lifecycle?\u003C\u002Fh3>\n\u003Cp>It is the ordered sequence Nuxt uses to start the app, resolve a route, run middleware, load data, render the page (often on the server), hydrate in the browser, and handle later client navigations. Vue component hooks sit inside that larger app flow.\u003C\u002Fp>\n\n\u003Ch3>How do I get started with Nuxt lifecycle concepts?\u003C\u002Fh3>\n\u003Cp>Build one SSR page that uses \u003Ccode>useFetch\u003C\u002Fcode>, add a tiny \u003Ccode>.client\u003C\u002Fcode> plugin, and one auth-style middleware. Then log messages with \u003Ccode>import.meta.server\u003C\u002Fcode> \u002F \u003Ccode>import.meta.client\u003C\u002Fcode> so you can see the order in the terminal and browser console.\u003C\u002Fp>\n\n\u003Ch3>Nuxt lifecycle vs Vue lifecycle?\u003C\u002Fh3>\n\u003Cp>Vue lifecycle is about one component (create → mount → update → unmount). Nuxt lifecycle includes that plus app boot, plugins, middleware, SSR render, payload transfer, hydration, and routing across pages.\u003C\u002Fp>\n\n\u003Ch3>Is understanding the Nuxt lifecycle worth it?\u003C\u002Fh3>\n\u003Cp>Yes — especially if you care about SEO, auth redirects, or “works locally but breaks in production” SSR bugs. A basic map saves hours of debugging.\u003C\u002Fp>\n\n\u003Ch3>When should I use \u003Ccode>onMounted\u003C\u002Fcode> in Nuxt?\u003C\u002Fh3>\n\u003Cp>Use it for browser-only work after the DOM exists: charts, focus management, third-party widgets, reading \u003Ccode>localStorage\u003C\u002Fcode>, measuring layout. Don’t rely on it for the main article\u002Fproduct content you want in the first HTML.\u003C\u002Fp>\n\n\u003Ch2>Summary\u003C\u002Fh2>\n\u003Cp>Nuxt’s lifecycle is not magic — it’s a predictable pipeline from request to interactive UI. Server work prepares HTML and data; client work activates the page and handles navigation.\u003C\u002Fp>\n\u003Cp>Once you separate “needs HTML for SEO” from “needs the browser,” most Nuxt bugs become easy to place. Plugins wire the app, middleware guards routes, data composables feed render, and component hooks finish client-side details.\u003C\u002Fp>\n\u003Cp>Start your next feature by naming the stage first. That one habit makes Nuxt apps calmer to build and safer to ship.\u003C\u002Fp>\n\n\u003Ch2>Key Takeaways\u003C\u002Fh2>\n\u003Cul>\n  \u003Cli>Nuxt lifecycle = boot → middleware → data → render → hydrate → navigate.\u003C\u002Fli>\n  \u003Cli>Server and client are different rooms — browser APIs belong on the client path.\u003C\u002Fli>\n  \u003Cli>Use \u003Ccode>useFetch\u003C\u002Fcode>\u002F\u003Ccode>useAsyncData\u003C\u002Fcode> for first-paint content; use \u003Ccode>onMounted\u003C\u002Fcode> for DOM\u002Fbrowser extras.\u003C\u002Fli>\n  \u003Cli>Stable SSR HTML prevents hydration mismatches.\u003C\u002Fli>\n  \u003Cli>Plugins wire, middleware guards, pages display — keep each job separate.\u003C\u002Fli>\n\u003C\u002Ful>","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785901639981-9tgcl5.webp","Nuxt Lifecycle Explained — SSR, Hooks & App Flow","Learn the Nuxt lifecycle in plain English: server render, hydration, plugins, middleware, and Vue hooks. Clear steps, examples, and FAQs.","",[19,20,21,22,23],"Nuxt","Vue","SSR","Lifecycle","JavaScript","published","2026-08-05T03:54:08.301+00:00",12,null,"2026-08-05T03:47:26.200376+00:00","2026-08-05T03:54:08.919676+00:00",[31,46,63,79,92,106,118,129,143,156,167,178,190,203,217,227,229,238,249,263,275,284,295,308],{"id":32,"title":33,"slug":34,"excerpt":35,"cover_image":36,"tags":37,"published_at":43,"updated_at":44,"view_count":45},"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",[38,39,40,41,42,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":47,"title":48,"slug":49,"excerpt":50,"cover_image":51,"tags":52,"published_at":60,"updated_at":61,"view_count":62},"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",[53,54,55,39,6,56,57,58,59],"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":64,"title":65,"slug":66,"excerpt":67,"cover_image":68,"tags":69,"published_at":76,"updated_at":77,"view_count":78},"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",[70,71,72,73,74,19,75],"Laravel","Sanctum","CSRF","419","SPA","API Authentication","2026-10-17T09:40:04.212+00:00","2026-10-17T09:40:06.051151+00:00",17,{"id":80,"title":81,"slug":82,"excerpt":83,"cover_image":84,"tags":85,"published_at":89,"updated_at":90,"view_count":91},"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,86,20,87,88],"ImageKit","TypeScript","SEO","2026-10-17T05:55:24.556+00:00","2026-10-17T05:55:24.735773+00:00",23,{"id":93,"title":94,"slug":95,"excerpt":96,"cover_image":97,"tags":98,"published_at":104,"updated_at":105,"view_count":62},"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",[99,100,101,102,103],"Apache","Ubuntu","Installation","Linux","Web Server","2026-09-09T03:49:25.809+00:00","2026-09-09T03:49:26.679843+00:00",{"id":107,"title":108,"slug":109,"excerpt":110,"cover_image":111,"tags":112,"published_at":115,"updated_at":116,"view_count":117},"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",[99,113,100,103,102,114],"Nginx","DevOps","2026-09-04T12:14:08.218+00:00","2026-09-04T12:14:08.430018+00:00",9,{"id":119,"title":120,"slug":121,"excerpt":122,"cover_image":123,"tags":124,"published_at":127,"updated_at":128,"view_count":26},"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",[125,100,113,102,126,114],"Virtual Host","VPS","2026-09-04T12:09:22.623+00:00","2026-09-04T12:09:22.931401+00:00",{"id":130,"title":131,"slug":132,"excerpt":133,"cover_image":134,"tags":135,"published_at":140,"updated_at":141,"view_count":142},"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",[70,136,137,138,139],"Queues","Jobs","PHP","backend","2026-08-21T04:36:56.222+00:00","2026-08-21T04:36:56.606735+00:00",20,{"id":144,"title":145,"slug":146,"excerpt":147,"cover_image":148,"tags":149,"published_at":153,"updated_at":154,"view_count":155},"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",[70,150,151,152,138],"Eloquent","N+1","performance","2026-08-20T04:17:43.609+00:00","2026-08-20T05:50:24.297698+00:00",14,{"id":157,"title":158,"slug":159,"excerpt":160,"cover_image":161,"tags":162,"published_at":164,"updated_at":165,"view_count":166},"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",[70,150,138,163,139],"ORM","2026-08-19T07:03:17.721+00:00","2026-08-20T04:19:08.829027+00:00",18,{"id":168,"title":169,"slug":170,"excerpt":171,"cover_image":172,"tags":173,"published_at":176,"updated_at":177,"view_count":62},"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",[70,174,150,138,175],"Database","Transactions","2026-08-19T04:44:00.327+00:00","2026-08-19T05:14:18.190197+00:00",{"id":179,"title":180,"slug":181,"excerpt":182,"cover_image":183,"tags":184,"published_at":188,"updated_at":189,"view_count":155},"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",[70,185,138,186,187],"Auditing","Security","Activity Log","2026-08-15T21:24:32.135+00:00","2026-08-15T21:24:32.194447+00:00",{"id":191,"title":192,"slug":193,"excerpt":194,"cover_image":195,"tags":196,"published_at":200,"updated_at":201,"view_count":202},"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",[70,138,197,198,199],"Request Lifecycle","Middleware","Backend","2026-08-15T07:15:13.877+00:00","2026-08-15T07:15:13.978037+00:00",11,{"id":204,"title":205,"slug":206,"excerpt":207,"cover_image":208,"tags":209,"published_at":215,"updated_at":216,"view_count":155},"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",[210,211,212,213,214],"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":218,"title":219,"slug":220,"excerpt":221,"cover_image":222,"tags":223,"published_at":225,"updated_at":226,"view_count":166},"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.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785902953511-osy6pt.webp",[19,198,21,224,20],"Auth","2026-08-05T04:09:38.347+00:00","2026-08-05T04:09:38.496803+00:00",{"id":9,"title":10,"slug":11,"excerpt":12,"cover_image":14,"tags":228,"published_at":25,"updated_at":29,"view_count":26},[19,20,21,22,23],{"id":230,"title":231,"slug":232,"excerpt":233,"cover_image":234,"tags":235,"published_at":236,"updated_at":237,"view_count":91},"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",[70,71,75,138,74,186],"2026-08-04T08:56:17.304+00:00","2026-08-06T04:07:09.059636+00:00",{"id":239,"title":240,"slug":241,"excerpt":242,"cover_image":243,"tags":244,"published_at":247,"updated_at":248,"view_count":166},"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",[70,71,245,75,138,246,74],"Passport","OAuth2","2026-08-04T04:19:37.286+00:00","2026-08-04T04:49:08.25034+00:00",{"id":250,"title":251,"slug":252,"excerpt":253,"cover_image":254,"tags":255,"published_at":260,"updated_at":261,"view_count":262},"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",[70,256,199,257,258,138,87,259],"NestJS","SaaS","Startups","Web Development","2026-08-01T18:40:05.071+00:00","2026-08-01T18:40:05.261242+00:00",38,{"id":264,"title":265,"slug":266,"excerpt":267,"cover_image":268,"tags":269,"published_at":273,"updated_at":274,"view_count":26},"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",[87,23,259,270,271,272],"Programming","Beginners","Frontend","2026-08-01T08:50:45.861+00:00","2026-08-01T08:50:45.958378+00:00",{"id":276,"title":277,"slug":278,"excerpt":279,"cover_image":280,"tags":281,"published_at":282,"updated_at":283,"view_count":155},"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",[23,259,270,271,272],"2026-08-01T05:16:12.728+00:00","2026-08-01T08:50:11.164531+00:00",{"id":285,"title":286,"slug":287,"excerpt":288,"cover_image":289,"tags":290,"published_at":293,"updated_at":294,"view_count":166},"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",[70,71,291,292,74],"API","Authentication","2026-08-01T04:13:15.178+00:00","2026-08-01T08:50:11.393519+00:00",{"id":296,"title":297,"slug":298,"excerpt":299,"cover_image":300,"tags":301,"published_at":305,"updated_at":306,"view_count":307},"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",[70,138,302,303,199,304],"Modules","Architecture","Clean Code","2026-07-30T04:54:17.431+00:00","2026-08-01T08:50:11.599795+00:00",6,{"id":309,"title":310,"slug":311,"excerpt":312,"cover_image":313,"tags":314,"published_at":321,"updated_at":322,"view_count":142},"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",[70,315,316,317,318,319,320],"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",{"variant":324,"profile":329,"heroStats":342,"aboutParagraphs":346,"aboutPillars":353,"aboutFacts":366,"skillCategories":379,"experiences":418,"education":445,"projects":464,"languages":534,"interests":537},{"id":325,"slug":326,"label":327,"is_active":328,"sort_order":4},"481b2725-e0f6-43df-beea-937ec806a438","full-stack-developer","Full Stack Developer",true,{"name":330,"title":331,"tagline":331,"photo_url":332,"summary":333,"email":334,"phone":17,"location":335,"linkedin":336,"github":337,"instagram":338,"hero_headline":339,"hero_headline_accent":340,"hero_subheadline":341},"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.",[343],{"value":344,"label":345},"3.5+","Yrs Development",[347,349,351],{"html":348},"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":350},"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":352},"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.",[354,358,362],{"icon":355,"label":356,"description":357},"lucide:code-2","Build","Scalable, clean web apps",{"icon":359,"label":360,"description":361},"lucide:trending-up","Grow","Marketing-driven results",{"icon":363,"label":364,"description":365},"lucide:shield-check","Ship","Reliable, compliant systems",[367,371,375],{"icon":368,"label":369,"value":370},"lucide:settings","Core Stack","Laravel · Nuxt · Vue · MySQL",{"icon":372,"label":373,"value":374},"lucide:building-2","Currently","Complibued — eQMS Platform",{"icon":376,"label":377,"value":378},"lucide:map-pin","Availability","Open to opportunities",[380,393,402,413],{"title":381,"icon":382,"color":383,"show_on_home":328,"show_on_resume":328,"skills":384},"Backend Development","lucide:database","from-gold-soft to-gold-deep",[70,138,385,386,387,388,389,390,391,392],"Supabase (BaaS)","MySQL","REST APIs","Git","Docker","Redis","GitHub Actions","Cloudflare",{"title":394,"icon":395,"color":383,"show_on_home":328,"show_on_resume":396,"skills":397},"Frontend Development","lucide:code",false,[398,399,400,87,401,23],"Nuxt.js","Vue.js","React","Tailwind CSS",{"title":403,"icon":404,"color":383,"show_on_home":328,"show_on_resume":396,"skills":405},"AI & Automation","lucide:zap",[406,407,408,409,410,411,412],"Prompt Engineering","ChatGPT & Claude","Google Gemini","AI Grok","GitHub Copilot","AI Content Strategy","Workflow Automation",{"title":414,"icon":415,"color":383,"show_on_home":328,"show_on_resume":328,"skills":416},"Development","lucide:wrench",[70,138,399,398,23,87,401,387,386,417],"Git & GitHub",[419],{"role":327,"company":420,"note":421,"period":422,"description":423,"stack":424,"color":383,"icon":425,"points":426},"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",[427,430,432,434,436,439,441,443],{"text":428,"surface":429},"Developing and maintaining a pharma-focused eQMS platform using Laravel and Nuxt.js.","resume",{"text":431,"surface":429},"Built compliance-critical modules: Document Control, Training (LMS), Event Handling, CAPA, Change Control (CR), Audit, and Risk Assessment (RA).",{"text":433,"surface":429},"Implemented approval workflows, version control, and immutable audit trails aligned to 21 CFR Part 11.",{"text":435,"surface":429},"Collaborated with QA teams to meet pharmaceutical compliance standards.",{"text":437,"surface":438},"Built Document Control & LMS (training) modules","home",{"text":440,"surface":438},"Implemented CAPA and Event management workflows",{"text":442,"surface":438},"Developed Change Control (CR) with impact-assessed approvals",{"text":444,"surface":438},"Delivered Audit & Risk Assessment (RA) modules with audit trails",[446,451,455,460],{"degree":447,"school":448,"period":449,"score":450},"M.Sc. (Computer Science)","MDS University, Ajmer","2023 – 2025","73%",{"degree":452,"school":448,"period":453,"score":454},"BCA","2020 – 2023","71%",{"degree":456,"school":457,"period":458,"score":459},"Senior Secondary (12th)","RBSE, Ajmer","2018 – 2019","68.80%",{"degree":461,"school":457,"period":462,"score":463},"Secondary (10th)","2016 – 2017","48.75%",[465,482,499],{"title":466,"slug":467,"description":468,"why":469,"category":470,"image":471,"emoji":472,"link":473,"is_active":328,"stack":474,"features":476,"metrics":481},"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",[399,475,386,401,87],"Supabase",[477,478,479,480],"Stock Tracking","Order Management","User Authentication","Reporting & Analytics",[],{"title":483,"slug":484,"description":485,"why":486,"category":487,"image":488,"emoji":489,"link":490,"is_active":328,"stack":491,"features":493,"metrics":498},"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",[399,492,475,401,87],"WebRTC",[494,495,496,497],"Peer-to-Peer Video","Random Matchmaking","Realtime Signaling","No Sign-up Required",[],{"title":500,"slug":501,"description":502,"why":503,"category":504,"image":488,"emoji":505,"link":506,"is_active":328,"stack":507,"features":515,"metrics":524},"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",[508,509,510,511,401,87,386,512,513,514,389],"Laravel 12","Nuxt 4","Vue 3","Vuetify 3","stancl\u002Ftenancy","Laravel Sanctum","Spatie Permission",[516,517,518,519,520,521,522,523],"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)",[525,528,531],{"value":526,"label":527},"1","Product platform",{"value":529,"label":530},"7+","Core modules",{"value":532,"label":533},"MT","Multi-tenant",[535,536],"Hindi","English",[259,538,539],"Video Content","New Tools & Tech",[]]