[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"site-settings":3,"blog-post:laravel-n-plus-1-query-problem":8,"blog-posts-latest:24":31,"site-content":324,"blog-comments:938c7bd9-2cf3-4a81-8dae-cf88c09e64ca":541},{"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":28,"created_at":29,"updated_at":30},"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.","\u003Ch2 id=\"quick-answer\">Quick Answer\u003C\u002Fh2>\n\u003Cp>N+1 is Eloquent being lazy in a loop. You load posts with one query, then \u003Ccode>$post-&gt;author\u003C\u002Fcode> or \u003Ccode>$post-&gt;comments\u003C\u002Fcode> fires a new SELECT for every row — 1+N, not a slow join. I look for it on index endpoints and Blade listings. Telescope (or a query log) shows the same SQL with a changing \u003Ccode>post_id\u003C\u002Fcode>. Put \u003Ccode>with()\u003C\u002Fcode> or \u003Ccode>withCount()\u003C\u002Fcode> on that listing query. Do not “fix” it inside the foreach.\u003C\u002Fp>\n\n\u003Ch2 id=\"quick-facts\">Quick Facts\u003C\u002Fh2>\n\u003Ctable>\n\u003Cthead>\u003Ctr>\u003Cth>Item\u003C\u002Fth>\u003Cth>Details\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\u003Ctd>Topic\u003C\u002Ftd>\u003Ctd>Laravel N+1 Query Problem\u003C\u002Ftd>\u003C\u002Ftr>\n\u003Ctr>\u003Ctd>Category\u003C\u002Ftd>\u003Ctd>Laravel \u002F Eloquent \u002F Performance\u003C\u002Ftd>\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\n\u003Cnav class=\"blog-toc\" aria-label=\"Table of contents\">\n\u003Ch2 id=\"table-of-contents\">Table of Contents\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"#what-is-laravel-n-1-query-problem\">What Is Laravel N+1 Query Problem?\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#why-it-matters\">Why It Matters\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#how-it-works\">How It Works\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#step-by-step-guide\">Step-by-Step Guide\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#real-world-example\">Real-World Example\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#pros-cons\">Pros &amp; Cons\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#best-practices\">Best Practices\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#common-mistakes\">Common Mistakes\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#frequently-asked-questions\">FAQs\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#key-takeaways\">Key Takeaways\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fnav>\n\n\u003Ch2 id=\"what-is-laravel-n-1-query-problem\">What Is Laravel N+1 Query Problem?\u003C\u002Fh2>\n\u003Cp>Laravel did not invent this. Any ORM will do it if you walk a collection and poke relations that were never loaded.\u003C\u002Fp>\n\u003Cp>Eloquent just makes it easy to miss. \u003Ccode>Post::latest()-&gt;get()\u003C\u002Fcode> looks finished. Then the resource or the Blade file reads \u003Ccode>$post-&gt;author-&gt;name\u003C\u002Fcode> and you get another round trip. Eight posts on your laptop? Fine. Two hundred on production and the same code sits in Telescope like a drumbeat: \u003Ccode>where post_id = 1\u003C\u002Fcode>, \u003Ccode>= 2\u003C\u002Fcode>, \u003Ccode>= 3\u003C\u002Fcode>…\u003C\u002Fp>\n\u003Cp>A slow join is one fat query. N+1 is a pile of skinny ones. If you already wired \u003Ca href=\"\u002Fblog\u002Flaravel-eloquent-relationships\">Eloquent relationships\u003C\u002Fa> and never called \u003Ccode>with()\u003C\u002Fcode>, you basically opted into this.\u003C\u002Fp>\n\n\u003Ch2 id=\"why-it-matters\">Why It Matters\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Page size 20 can already be ~60 queries if you touch author, tags, and comments. Bump to 100 and you are in the hundreds. The app does not “feel a bit slow.” Connections stack up.\u003C\u002Fli>\n\u003Cli>\u003Ccode>$post-&gt;author-&gt;name\u003C\u002Fcode> is the kind of line nobody flags in review. It only blows up in a loop.\u003C\u002Fli>\n\u003Cli>JSON APIs fail first. The SPA still paints a skeleton; the DB is already busy. I have watched Nuxt wait on \u003Ccode>\u002Fapi\u002Fposts\u003C\u002Fcode> while Laravel burned a query per field per row.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2 id=\"how-it-works\">How It Works\u003C\u002Fh2>\n\u003Cp>Parents load. Relations stay empty until you read them as a property. Property access in a loop = one query per parent. That is the whole trick.\u003C\u002Fp>\n\n\u003Cfigure class=\"blog-figure blog-figure--diagram\" contenteditable=\"false\">\n\u003Cdiv class=\"blog-mermaid\">\n\u003Cpre class=\"mermaid-source\">flowchart TB\n  Q0[\"Query 0: SELECT * FROM posts\"]\n  Q0 --> P1[Post 1]\n  Q0 --> P2[Post 2]\n  Q0 --> PN[Post N]\n  P1 --> Q1[\"Query 1: comments WHERE post_id = 1\"]\n  P2 --> Q2[\"Query 2: comments WHERE post_id = 2\"]\n  PN --> QN[\"Query N: comments WHERE post_id = N\"]\u003C\u002Fpre>\n\u003C\u002Fdiv>\n\u003Cfigcaption>This is what Telescope looks like: one posts query, then comments over and over.\u003C\u002Ffigcaption>\n\u003C\u002Ffigure>\n\n\u003Cp>\u003Ccode>with('comments')\u003C\u002Fcode> changes the second step. Eloquent grabs the post ids and runs one \u003Ccode>WHERE post_id IN (…)\u003C\u002Fcode>. Same comments. Query count stops tracking how many cards you rendered.\u003C\u002Fp>\n\n\u003Cfigure class=\"blog-figure blog-figure--diagram\" contenteditable=\"false\">\n\u003Cdiv class=\"blog-mermaid\">\n\u003Cpre class=\"mermaid-source\">flowchart LR\n  A[\"Query 1: SELECT * FROM posts\"] --> B[\"Collect post ids: 1,2,…N\"]\n  B --> C[\"Query 2: SELECT * FROM comments WHERE post_id IN (…)\"]\n  C --> D[\"Attach comments onto each Post in memory\"]\u003C\u002Fpre>\n\u003C\u002Fdiv>\n\u003Cfigcaption>Two trips for one relation. Add more posts to the page — still two trips.\u003C\u002Ffigcaption>\n\u003C\u002Ffigure>\n\n\u003Cp>I keep three cases in my head:\u003C\u002Fp>\n\u003Col>\n\u003Cli>You actually need the related models → \u003Ccode>with('comments')\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>The UI only shows “12 comments” → \u003Ccode>withCount('comments')\u003C\u002Fcode> and read \u003Ccode>comments_count\u003C\u002Fcode>. Hydrating twelve Comment models to call \u003Ccode>-&gt;count()\u003C\u002Fcode> is how memory dies on a popular post.\u003C\u002Fli>\n\u003Cli>You already have the collection in hand → \u003Ccode>$posts-&gt;load('tags')\u003C\u002Fcode> once. Not \u003Ccode>$post-&gt;load()\u003C\u002Fcode> inside foreach. That last one is still N+1 with extra steps.\u003C\u002Fli>\n\u003C\u002Fol>\n\n\u003Cfigure class=\"blog-figure blog-figure--diagram\" contenteditable=\"false\">\n\u003Cdiv class=\"blog-mermaid\">\n\u003Cpre class=\"mermaid-source\">flowchart TB\n  subgraph bad [Need only a number]\n    B1[Load all Comment models] --> B2[Call count in PHP]\n  end\n  subgraph good [Need only a number]\n    G1[\"withCount comments\"] --> G2[\"comments_count on Post\"]\n  end\u003C\u002Fpre>\n\u003C\u002Fdiv>\n\u003Cfigcaption>Badge on the card vs loading the whole thread. withCount is the badge.\u003C\u002Ffigcaption>\n\u003C\u002Ffigure>\n\n\u003Ch2 id=\"step-by-step-guide\">Step-by-Step Guide\u003C\u002Fh2>\n\n\u003Ch3 id=\"step-1\">Step 1: Prove the query count\u003C\u002Fh3>\n\u003Cp>Guessing wastes time. Hit the slow URL with Telescope Queries open. Debugbar works. So does a dirty \u003Ccode>DB::listen(fn ($q) =&gt; logger($q-&gt;sql));\u003C\u002Fcode> if you are stuck without those.\u003C\u002Fp>\n\n\u003Cfigure class=\"blog-figure blog-figure--diagram\" contenteditable=\"false\">\n\u003Cdiv class=\"blog-mermaid\">\n\u003Cpre class=\"mermaid-source\">flowchart LR\n  Hit[Hit \u002Fposts index] --> Log[Open Telescope Queries]\n  Log --> Pattern{\"Same SQL repeating with different post_id?\"}\n  Pattern -->|Yes| N1[You have N+1]\n  Pattern -->|No| Other[Look for slow join \u002F missing index]\u003C\u002Fpre>\n\u003C\u002Fdiv>\n\u003Cfigcaption>Repeating relation SQL with a new id each line = N+1. One ugly 800ms join is a different ticket.\u003C\u002Ffigcaption>\n\u003C\u002Ffigure>\n\n\u003Cp>Write the number down. Something like “20 posts, 61 queries.” If you skip that, you will swear you fixed it and never re-check.\u003C\u002Fp>\n\n\u003Ch3 id=\"step-2\">Step 2: Eager-load on the root query\u003C\u002Fh3>\n\u003Cp>The listing query is the place. Controller, invokable, a \u003Ccode>scopeIndex()\u003C\u002Fcode> — I do not care, as long as it is not the Blade loop.\u003C\u002Fp>\n\n\u003Cfigure class=\"blog-figure blog-figure--diagram\" contenteditable=\"false\">\n\u003Cdiv class=\"blog-mermaid\">\n\u003Cpre class=\"mermaid-source\">flowchart TB\n  subgraph before [Before]\n    C1[Controller: Post::latest get] --> L1[Loop \u002F serializer]\n    L1 --> R1[\"Touch author, tags, comments\"]\n  end\n  subgraph after [After]\n    C2[\"Controller: Post::with author tags + withCount comments\"] --> L2[Loop \u002F serializer]\n    L2 --> R2[Relations already loaded]\n  end\u003C\u002Fpre>\n\u003C\u002Fdiv>\n\u003Cfigcaption>Serializer can keep touching \u003Ccode>$this-&gt;author\u003C\u002Fcode>. The query has to have loaded it already.\u003C\u002Ffigcaption>\n\u003C\u002Ffigure>\n\n\u003Cpre>\u003Ccode class=\"language-php\">\u002F\u002F Before — looks innocent, scales badly\n$posts = Post::latest()-&gt;paginate(20);\n\n\u002F\u002F After — relations declared up front\n$posts = Post::query()\n    -&gt;with(['author', 'tags'])\n    -&gt;withCount('comments')\n    -&gt;latest()\n    -&gt;paginate(20);\u003C\u002Fcode>\u003C\u002Fpre>\n\n\u003Cp>Need the comment author’s name too? Dot path:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-php\">Post::with(['comments.author', 'tags'])-&gt;paginate(20);\u003C\u002Fcode>\u003C\u002Fpre>\n\n\u003Cfigure class=\"blog-figure blog-figure--diagram\" contenteditable=\"false\">\n\u003Cdiv class=\"blog-mermaid\">\n\u003Cpre class=\"mermaid-source\">flowchart LR\n  P[posts] --> C[comments]\n  C --> A[users as author]\n  P --> T[tags]\u003C\u002Fpre>\n\u003C\u002Fdiv>\n\u003Cfigcaption>\u003Ccode>comments.author\u003C\u002Fcode> means load comments, then the author on those comments. Miss the nested bit and you N+1 the users table next.\u003C\u002Ffigcaption>\n\u003C\u002Ffigure>\n\n\u003Cp>Sanity check: bump \u003Ccode>per_page\u003C\u002Fcode> from 10 to 50. Query count should barely move. If it climbs, you still have a lazy relation — usually one you added to the Resource last Thursday.\u003C\u002Fp>\n\n\u003Ch3 id=\"step-3\">Step 3: Guard so it cannot sneak back\u003C\u002Fh3>\n\u003Cp>Local\u002Fstaging only:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-php\">\u002F\u002F AppServiceProvider::boot() — local only\nModel::preventLazyLoading(! app()-&gt;isProduction());\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Forget \u003Ccode>with('tags')\u003C\u002Fcode> and you get \u003Ccode>LazyLoadingViolationException\u003C\u002Fcode> instead of a silent production bill. I still list \u003Ccode>with()\u003C\u002Fcode> \u002F \u003Ccode>withCount()\u003C\u002Fcode> on the same lines as \u003Ccode>paginate()\u003C\u002Fcode> so the next person sees the contract.\u003C\u002Fp>\n\u003Cp>If you want to be mean in tests, trigger a lazy load on purpose once and assert it throws. Then leave the real index green with eager loads in place.\u003C\u002Fp>\n\n\u003Ch2 id=\"real-world-example\">Real-World Example\u003C\u002Fh2>\n\u003Cp>Laravel 11 API, Nuxt admin, \u003Ccode>GET \u002Fapi\u002Fposts\u003C\u002Fcode>. Payload: title, author name, tag names, comment count.\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-php\">return PostResource::collection(Post::latest()-&gt;paginate(50));\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Resource:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-php\">'author' =&gt; $this-&gt;author-&gt;name,\n'tags' =&gt; $this-&gt;tags-&gt;pluck('name'),\n'comments_count' =&gt; $this-&gt;comments-&gt;count(),\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Local fixture had a dozen posts. Nobody opened Telescope. Production paginated 50. Gateway timeout. Telescope was almost funny: posts once, then users \u002F pivot \u002F comments × 50.\u003C\u002Fp>\n\n\u003Cfigure class=\"blog-figure blog-figure--diagram\" contenteditable=\"false\">\n\u003Cdiv class=\"blog-mermaid\">\n\u003Cpre class=\"mermaid-source\">sequenceDiagram\n  participant Nuxt\n  participant API\n  participant DB\n  Nuxt-&gt;&gt;API: GET \u002Fapi\u002Fposts?page=1\n  API-&gt;&gt;DB: SELECT * FROM posts LIMIT 50\n  loop For each of 50 posts\n    API-&gt;&gt;DB: SELECT * FROM users WHERE id = ?\n    API-&gt;&gt;DB: SELECT tags via post_tag\n    API-&gt;&gt;DB: SELECT * FROM comments WHERE post_id = ?\n  end\n  Note over API,DB: ~1 + 150 queries. Timeout under load.\u003C\u002Fpre>\n\u003C\u002Fdiv>\n\u003Cfigcaption>Three relations per row, fifty rows. You do the math. I did it after the timeout.\u003C\u002Ffigcaption>\n\u003C\u002Ffigure>\n\n\u003Cpre>\u003Ccode class=\"language-php\">$posts = Post::query()\n    -&gt;with(['author', 'tags'])\n    -&gt;withCount('comments')\n    -&gt;latest()\n    -&gt;paginate(50);\n\n\u002F\u002F resource:\n'comments_count' =&gt; $this-&gt;comments_count,\u003C\u002Fcode>\u003C\u002Fpre>\n\n\u003Cfigure class=\"blog-figure blog-figure--diagram\" contenteditable=\"false\">\n\u003Cdiv class=\"blog-mermaid\">\n\u003Cpre class=\"mermaid-source\">sequenceDiagram\n  participant Nuxt\n  participant API\n  participant DB\n  Nuxt-&gt;&gt;API: GET \u002Fapi\u002Fposts?page=1\n  API-&gt;&gt;DB: SELECT * FROM posts LIMIT 50\n  API-&gt;&gt;DB: SELECT * FROM users WHERE id IN (…)\n  API-&gt;&gt;DB: SELECT post_tag \u002F tags for those posts\n  API-&gt;&gt;DB: aggregate comments_count per post\n  Note over API,DB: Query count stays flat when page size grows.\u003C\u002Fpre>\n\u003C\u002Fdiv>\n\u003Cfigcaption>Same JSON shape. \u003Ccode>comments_count\u003C\u002Fcode> is an attribute now, not a loaded collection.\u003C\u002Ffigcaption>\n\u003C\u002Ffigure>\n\n\u003Cp>Same PR had a second bug that looked like N+1 but was not: \u003Ccode>author_id\u003C\u002Fcode> on posts, \u003Ccode>belongsTo(User::class)\u003C\u002Fcode> with no extra argument. SQL wanted \u003Ccode>user_id\u003C\u002Fcode>. Authors came back null. Eager loading will happily load nothing. Pass the key.\u003C\u002Fp>\n\n\u003Ch2 id=\"pros-cons\">Pros &amp; Cons\u003C\u002Fh2>\n\u003Ch3>Advantages\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Once you know which keys the Resource touches, the fix is usually one \u003Ccode>with()\u003C\u002Fcode> line.\u003C\u002Fli>\n\u003Cli>Telescope makes the pattern obvious. You are not profiling vibes.\u003C\u002Fli>\n\u003Cli>\u003Ccode>preventLazyLoading()\u003C\u002Fcode> is annoying in local and that is the point.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Disadvantages\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ccode>with('everything')\u003C\u002Fcode> on every query is how you over-fetch. Load what this response uses.\u003C\u002Fli>\n\u003Cli>\u003Ccode>a.b.c.d\u003C\u002Fcode> still hurts. At some point a dedicated query or a cached fragment is less cute and faster.\u003C\u002Fli>\n\u003Cli>Nothing in PHP forces this. Ship without Telescope and you will rediscover it in prod.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2 id=\"best-practices\">Best Practices\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Keep \u003Ccode>with()\u003C\u002Fcode> \u002F \u003Ccode>withCount()\u003C\u002Fcode> next to the \u003Ccode>paginate()\u003C\u002Fcode> that feeds the Resource. Future you will not hunt two files.\u003C\u002Fli>\n\u003Cli>Number on the card → \u003Ccode>withCount\u003C\u002Fcode>. Full nested objects → \u003Ccode>with\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>After you add a field to an API Resource, open Telescope again. That field is how N+1 comes back.\u003C\u002Fli>\n\u003Cli>\u003Ccode>preventLazyLoading()\u003C\u002Fcode> outside production. Production should already have the loads; the guard is a seatbelt for the next PR.\u003C\u002Fli>\n\u003Cli>Conditional includes: either \u003Ccode>with()\u003C\u002Fcode> only what the request asked for, or \u003Ccode>whenLoaded\u003C\u002Fcode> in the Resource so a missing eager load fails loudly instead of lazy-loading.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2 id=\"common-mistakes\">Common Mistakes\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ccode>foreach ($posts as $p) { $p-&gt;load('tags'); }\u003C\u002Fcode> — still N queries. Load the collection once: \u003Ccode>$posts-&gt;load('tags')\u003C\u002Fcode>, or \u003Ccode>with()\u003C\u002Fcode> up front.\u003C\u002Fli>\n\u003Cli>\u003Ccode>$this-&gt;comments-&gt;count()\u003C\u002Fcode> in a Resource. That pulls every comment. \u003Ccode>withCount('comments')\u003C\u002Fcode>, then \u003Ccode>$this-&gt;comments_count\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>Relation method is \u003Ccode>author()\u003C\u002Fcode>, you wrote \u003Ccode>with('user')\u003C\u002Fcode>. Eloquent will not guess. Match the method name.\u003C\u002Fli>\n\u003Cli>You added a \u003Ccode>join\u003C\u002Fcode> and assumed you were done, then the Resource still lazy-loads tags. Check the log anyway.\u003C\u002Fli>\n\u003Cli>\u003Ccode>$post-&gt;comments-&gt;where('approved', true)\u003C\u002Fcode> filters in memory after a full load. Constrain the query: \u003Ccode>$post-&gt;comments()-&gt;where('approved', true)-&gt;get()\u003C\u002Fcode>, or \u003Ccode>with(['comments' =&gt; fn ($q) =&gt; $q-&gt;where('approved', true)])\u003C\u002Fcode>.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2 id=\"frequently-asked-questions\">Frequently Asked Questions\u003C\u002Fh2>\n\u003Ch3 id=\"faq-what-is-laravel-n-1-query-problem\">What is the Laravel N+1 query problem?\u003C\u002Fh3>\n\u003Cp>One query loads the list. Each row then triggers another query for a relation. Total is about 1+N, or 1+N times how many relations you touch. \u003Ccode>with()\u003C\u002Fcode> \u002F \u003Ccode>withCount()\u003C\u002Fcode> load those rows in bulk so the count stays small.\u003C\u002Fp>\n\u003Ch3 id=\"faq-how-to\">How do I detect N+1 in Laravel?\u003C\u002Fh3>\n\u003Cp>Telescope on the slow page. Same relation SQL, different parent ids, over and over. Raise \u003Ccode>per_page\u003C\u002Fcode>. If queries climb with rows, you are not done.\u003C\u002Fp>\n\u003Ch3 id=\"faq-vs\">N+1 vs a slow join?\u003C\u002Fh3>\n\u003Cp>N+1 is many small queries that scale with rows — eager load. A slow join is one heavy query — indexes, fewer columns, sometimes raw SQL. Mixing them up wastes a day.\u003C\u002Fp>\n\u003Ch3 id=\"faq-worth-it\">Is fixing N+1 worth it?\u003C\u002Fh3>\n\u003Cp>On any listing that touches relations, yes. Local seed data hides it. Production page size does not. I have seen a five-minute \u003Ccode>with()\u003C\u002Fcode> remove timeouts people were blaming on the server.\u003C\u002Fp>\n\u003Ch3 id=\"faq-with-vs-load\">What is the difference between with() and load()?\u003C\u002Fh3>\n\u003Cp>\u003Ccode>with()\u003C\u002Fcode> hangs off the query builder before models exist. \u003Ccode>load()\u003C\u002Fcode> is for a collection you already have. Both are fine. \u003Ccode>load()\u003C\u002Fcode> inside a per-item loop is not.\u003C\u002Fp>\n\n\u003Ch2 id=\"summary\">Summary\u003C\u002Fh2>\n\u003Cp>N+1 is lazy relations in a loop. Telescope repeats the SQL. The fix sits on the listing query: \u003Ccode>with()\u003C\u002Fcode>, \u003Ccode>withCount()\u003C\u002Fcode>, nested dots if you need them. Local \u003Ccode>preventLazyLoading()\u003C\u002Fcode> stops the next PR from undoing it quietly.\u003C\u002Fp>\n\u003Cp>Pick the fattest index you have, note the query count, add the missing loads, raise \u003Ccode>per_page\u003C\u002Fcode>, confirm the count stays boring.\u003C\u002Fp>\n\u003Cp>Related: \u003Ca href=\"\u002Fblog\u002Flaravel-eloquent-relationships\">Laravel Eloquent Relationships\u003C\u002Fa>.\u003C\u002Fp>\n\n\u003Ch2 id=\"key-takeaways\">Key Takeaways\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>N+1 = one parent query plus one relation query per row (times each relation you touch).\u003C\u002Fli>\n\u003Cli>Telescope repeating the same SQL with a new id is the tell. Do not argue with the log.\u003C\u002Fli>\n\u003Cli>Fix on the root query. \u003Ccode>withCount\u003C\u002Fcode> when you only need a number.\u003C\u002Fli>\n\u003Cli>Nested data uses dots: \u003Ccode>with(['comments.author'])\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Ccode>preventLazyLoading()\u003C\u002Fcode> in local is louder than a production timeout.\u003C\u002Fli>\n\u003C\u002Ful>","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1787199419649-niq9k8.webp","Laravel N+1 Query Problem: Detect & Fix","Spot Laravel N+1 with Telescope and the query log, then fix it with with(), withCount(), and nested eager loading. Diagrams + a real listing timeout case.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fog\u002F1787199456113-smptxa.webp",[19,20,21,22,23],"Laravel","Eloquent","N+1","performance","PHP","published","2026-08-20T04:17:43.609+00:00",14,null,"","2026-08-20T04:17:44.134115+00:00","2026-08-20T05:50:24.297698+00:00",[32,47,64,80,94,108,120,132,145,147,158,169,181,194,208,219,230,239,250,264,276,285,296,309],{"id":33,"title":34,"slug":35,"excerpt":36,"cover_image":37,"tags":38,"published_at":44,"updated_at":45,"view_count":46},"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",[39,40,41,42,43,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":48,"title":49,"slug":50,"excerpt":51,"cover_image":52,"tags":53,"published_at":61,"updated_at":62,"view_count":63},"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",[54,55,56,40,6,57,58,59,60],"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":65,"title":66,"slug":67,"excerpt":68,"cover_image":69,"tags":70,"published_at":77,"updated_at":78,"view_count":79},"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",[19,71,72,73,74,75,76],"Sanctum","CSRF","419","SPA","Nuxt","API Authentication","2026-10-17T09:40:04.212+00:00","2026-10-17T09:40:06.051151+00:00",17,{"id":81,"title":82,"slug":83,"excerpt":84,"cover_image":85,"tags":86,"published_at":91,"updated_at":92,"view_count":93},"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",[75,87,88,89,90],"ImageKit","Vue","TypeScript","SEO","2026-10-17T05:55:24.556+00:00","2026-10-17T05:55:24.735773+00:00",23,{"id":95,"title":96,"slug":97,"excerpt":98,"cover_image":99,"tags":100,"published_at":106,"updated_at":107,"view_count":63},"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",[101,102,103,104,105],"Apache","Ubuntu","Installation","Linux","Web Server","2026-09-09T03:49:25.809+00:00","2026-09-09T03:49:26.679843+00:00",{"id":109,"title":110,"slug":111,"excerpt":112,"cover_image":113,"tags":114,"published_at":117,"updated_at":118,"view_count":119},"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",[101,115,102,105,104,116],"Nginx","DevOps","2026-09-04T12:14:08.218+00:00","2026-09-04T12:14:08.430018+00:00",9,{"id":121,"title":122,"slug":123,"excerpt":124,"cover_image":125,"tags":126,"published_at":129,"updated_at":130,"view_count":131},"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",[127,102,115,104,128,116],"Virtual Host","VPS","2026-09-04T12:09:22.623+00:00","2026-09-04T12:09:22.931401+00:00",12,{"id":133,"title":134,"slug":135,"excerpt":136,"cover_image":137,"tags":138,"published_at":142,"updated_at":143,"view_count":144},"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",[19,139,140,23,141],"Queues","Jobs","backend","2026-08-21T04:36:56.222+00:00","2026-08-21T04:36:56.606735+00:00",20,{"id":9,"title":10,"slug":11,"excerpt":12,"cover_image":14,"tags":146,"published_at":25,"updated_at":30,"view_count":26},[19,20,21,22,23],{"id":148,"title":149,"slug":150,"excerpt":151,"cover_image":152,"tags":153,"published_at":155,"updated_at":156,"view_count":157},"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",[19,20,23,154,141],"ORM","2026-08-19T07:03:17.721+00:00","2026-08-20T04:19:08.829027+00:00",18,{"id":159,"title":160,"slug":161,"excerpt":162,"cover_image":163,"tags":164,"published_at":167,"updated_at":168,"view_count":63},"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",[19,165,20,23,166],"Database","Transactions","2026-08-19T04:44:00.327+00:00","2026-08-19T05:14:18.190197+00:00",{"id":170,"title":171,"slug":172,"excerpt":173,"cover_image":174,"tags":175,"published_at":179,"updated_at":180,"view_count":26},"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",[19,176,23,177,178],"Auditing","Security","Activity Log","2026-08-15T21:24:32.135+00:00","2026-08-15T21:24:32.194447+00:00",{"id":182,"title":183,"slug":184,"excerpt":185,"cover_image":186,"tags":187,"published_at":191,"updated_at":192,"view_count":193},"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",[19,23,188,189,190],"Request Lifecycle","Middleware","Backend","2026-08-15T07:15:13.877+00:00","2026-08-15T07:15:13.978037+00:00",11,{"id":195,"title":196,"slug":197,"excerpt":198,"cover_image":199,"tags":200,"published_at":206,"updated_at":207,"view_count":26},"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",[201,202,203,204,205],"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":209,"title":210,"slug":211,"excerpt":212,"cover_image":213,"tags":214,"published_at":217,"updated_at":218,"view_count":157},"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",[75,189,215,216,88],"SSR","Auth","2026-08-05T04:09:38.347+00:00","2026-08-05T04:09:38.496803+00:00",{"id":220,"title":221,"slug":222,"excerpt":223,"cover_image":224,"tags":225,"published_at":228,"updated_at":229,"view_count":131},"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",[75,88,215,226,227],"Lifecycle","JavaScript","2026-08-05T03:54:08.301+00:00","2026-08-05T03:54:08.919676+00:00",{"id":231,"title":232,"slug":233,"excerpt":234,"cover_image":235,"tags":236,"published_at":237,"updated_at":238,"view_count":93},"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",[19,71,76,23,74,177],"2026-08-04T08:56:17.304+00:00","2026-08-06T04:07:09.059636+00:00",{"id":240,"title":241,"slug":242,"excerpt":243,"cover_image":244,"tags":245,"published_at":248,"updated_at":249,"view_count":157},"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",[19,71,246,76,23,247,74],"Passport","OAuth2","2026-08-04T04:19:37.286+00:00","2026-08-04T04:49:08.25034+00:00",{"id":251,"title":252,"slug":253,"excerpt":254,"cover_image":255,"tags":256,"published_at":261,"updated_at":262,"view_count":263},"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",[19,257,190,258,259,23,89,260],"NestJS","SaaS","Startups","Web Development","2026-08-01T18:40:05.071+00:00","2026-08-01T18:40:05.261242+00:00",38,{"id":265,"title":266,"slug":267,"excerpt":268,"cover_image":269,"tags":270,"published_at":274,"updated_at":275,"view_count":131},"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",[89,227,260,271,272,273],"Programming","Beginners","Frontend","2026-08-01T08:50:45.861+00:00","2026-08-01T08:50:45.958378+00:00",{"id":277,"title":278,"slug":279,"excerpt":280,"cover_image":281,"tags":282,"published_at":283,"updated_at":284,"view_count":26},"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",[227,260,271,272,273],"2026-08-01T05:16:12.728+00:00","2026-08-01T08:50:11.164531+00:00",{"id":286,"title":287,"slug":288,"excerpt":289,"cover_image":290,"tags":291,"published_at":294,"updated_at":295,"view_count":157},"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",[19,71,292,293,74],"API","Authentication","2026-08-01T04:13:15.178+00:00","2026-08-01T08:50:11.393519+00:00",{"id":297,"title":298,"slug":299,"excerpt":300,"cover_image":301,"tags":302,"published_at":306,"updated_at":307,"view_count":308},"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",[19,23,303,304,190,305],"Modules","Architecture","Clean Code","2026-07-30T04:54:17.431+00:00","2026-08-01T08:50:11.599795+00:00",6,{"id":310,"title":311,"slug":312,"excerpt":313,"cover_image":314,"tags":315,"published_at":322,"updated_at":323,"view_count":144},"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",[19,316,317,318,319,320,321],"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":325,"profile":330,"heroStats":343,"aboutParagraphs":347,"aboutPillars":354,"aboutFacts":367,"skillCategories":380,"experiences":419,"education":446,"projects":465,"languages":535,"interests":538},{"id":326,"slug":327,"label":328,"is_active":329,"sort_order":4},"481b2725-e0f6-43df-beea-937ec806a438","full-stack-developer","Full Stack Developer",true,{"name":331,"title":332,"tagline":332,"photo_url":333,"summary":334,"email":335,"phone":28,"location":336,"linkedin":337,"github":338,"instagram":339,"hero_headline":340,"hero_headline_accent":341,"hero_subheadline":342},"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.",[344],{"value":345,"label":346},"3.5+","Yrs Development",[348,350,352],{"html":349},"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":351},"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":353},"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.",[355,359,363],{"icon":356,"label":357,"description":358},"lucide:code-2","Build","Scalable, clean web apps",{"icon":360,"label":361,"description":362},"lucide:trending-up","Grow","Marketing-driven results",{"icon":364,"label":365,"description":366},"lucide:shield-check","Ship","Reliable, compliant systems",[368,372,376],{"icon":369,"label":370,"value":371},"lucide:settings","Core Stack","Laravel · Nuxt · Vue · MySQL",{"icon":373,"label":374,"value":375},"lucide:building-2","Currently","Complibued — eQMS Platform",{"icon":377,"label":378,"value":379},"lucide:map-pin","Availability","Open to opportunities",[381,394,403,414],{"title":382,"icon":383,"color":384,"show_on_home":329,"show_on_resume":329,"skills":385},"Backend Development","lucide:database","from-gold-soft to-gold-deep",[19,23,386,387,388,389,390,391,392,393],"Supabase (BaaS)","MySQL","REST APIs","Git","Docker","Redis","GitHub Actions","Cloudflare",{"title":395,"icon":396,"color":384,"show_on_home":329,"show_on_resume":397,"skills":398},"Frontend Development","lucide:code",false,[399,400,401,89,402,227],"Nuxt.js","Vue.js","React","Tailwind CSS",{"title":404,"icon":405,"color":384,"show_on_home":329,"show_on_resume":397,"skills":406},"AI & Automation","lucide:zap",[407,408,409,410,411,412,413],"Prompt Engineering","ChatGPT & Claude","Google Gemini","AI Grok","GitHub Copilot","AI Content Strategy","Workflow Automation",{"title":415,"icon":416,"color":384,"show_on_home":329,"show_on_resume":329,"skills":417},"Development","lucide:wrench",[19,23,400,399,227,89,402,388,387,418],"Git & GitHub",[420],{"role":328,"company":421,"note":422,"period":423,"description":424,"stack":425,"color":384,"icon":426,"points":427},"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",[428,431,433,435,437,440,442,444],{"text":429,"surface":430},"Developing and maintaining a pharma-focused eQMS platform using Laravel and Nuxt.js.","resume",{"text":432,"surface":430},"Built compliance-critical modules: Document Control, Training (LMS), Event Handling, CAPA, Change Control (CR), Audit, and Risk Assessment (RA).",{"text":434,"surface":430},"Implemented approval workflows, version control, and immutable audit trails aligned to 21 CFR Part 11.",{"text":436,"surface":430},"Collaborated with QA teams to meet pharmaceutical compliance standards.",{"text":438,"surface":439},"Built Document Control & LMS (training) modules","home",{"text":441,"surface":439},"Implemented CAPA and Event management workflows",{"text":443,"surface":439},"Developed Change Control (CR) with impact-assessed approvals",{"text":445,"surface":439},"Delivered Audit & Risk Assessment (RA) modules with audit trails",[447,452,456,461],{"degree":448,"school":449,"period":450,"score":451},"M.Sc. (Computer Science)","MDS University, Ajmer","2023 – 2025","73%",{"degree":453,"school":449,"period":454,"score":455},"BCA","2020 – 2023","71%",{"degree":457,"school":458,"period":459,"score":460},"Senior Secondary (12th)","RBSE, Ajmer","2018 – 2019","68.80%",{"degree":462,"school":458,"period":463,"score":464},"Secondary (10th)","2016 – 2017","48.75%",[466,483,500],{"title":467,"slug":468,"description":469,"why":470,"category":471,"image":472,"emoji":473,"link":474,"is_active":329,"stack":475,"features":477,"metrics":482},"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",[400,476,387,402,89],"Supabase",[478,479,480,481],"Stock Tracking","Order Management","User Authentication","Reporting & Analytics",[],{"title":484,"slug":485,"description":486,"why":487,"category":488,"image":489,"emoji":490,"link":491,"is_active":329,"stack":492,"features":494,"metrics":499},"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",[400,493,476,402,89],"WebRTC",[495,496,497,498],"Peer-to-Peer Video","Random Matchmaking","Realtime Signaling","No Sign-up Required",[],{"title":501,"slug":502,"description":503,"why":504,"category":505,"image":489,"emoji":506,"link":507,"is_active":329,"stack":508,"features":516,"metrics":525},"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",[509,510,511,512,402,89,387,513,514,515,390],"Laravel 12","Nuxt 4","Vue 3","Vuetify 3","stancl\u002Ftenancy","Laravel Sanctum","Spatie Permission",[517,518,519,520,521,522,523,524],"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)",[526,529,532],{"value":527,"label":528},"1","Product platform",{"value":530,"label":531},"7+","Core modules",{"value":533,"label":534},"MT","Multi-tenant",[536,537],"Hindi","English",[260,539,540],"Video Content","New Tools & Tech",[]]