[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"site-settings":3,"blog-post:laravel-lifecycle":8,"blog-comments:3d5eb867-6288-48c4-af04-8b7ece8b874e":30,"site-content":31,"blog-posts-latest:24":251},{"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},"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.","\u003Ch2>Quick Answer\u003C\u002Fh2>\n\u003Cp>The Laravel lifecycle is the ordered path an HTTP request takes: public\u002Findex.php boots the app, service providers register and boot, the HTTP kernel runs middleware, the router matches a route, a controller (or closure) runs, then Laravel sends a response and fires terminate callbacks. If you know that order, 404s, 419 CSRF errors, and “middleware never ran” bugs become easier to locate.\u003C\u002Fp>\n\n\u003Ch2>Quick Facts\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Topic:\u003C\u002Fstrong> Laravel Lifecycle\u003Cbr>\n\u003Cstrong>Category:\u003C\u002Fstrong> Backend \u002F Laravel Internals\u003C\u002Fp>\n\n\u003Ch2>Table of Contents\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>What Is Laravel 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 Laravel Lifecycle?\u003C\u002Fh2>\n\u003Cp>Laravel lifecycle means the request-to-response pipeline. A browser hits \u003Ccode>\u002Flogin\u003C\u002Fcode>, PHP starts at \u003Ccode>public\u002Findex.php\u003C\u002Fcode>, Laravel builds the application container, and the request walks through kernel, middleware, route, and controller before HTML or JSON comes back.\u003C\u002Fp>\n\u003Cp>People also say “application lifecycle” for artisan commands. Same idea: bootstrap, providers, then the job. This post sticks to HTTP, because that’s where most production issues show up.\u003C\u002Fp>\n\u003Cp>If you ship Laravel APIs with Vue or Nuxt, this pipeline is why Sanctum CSRF cookies, CORS, and \u003Ccode>auth:sanctum\u003C\u002Fcode> fail in specific spots—not “everywhere.” See \u003Ca href=\"\u002Fblog\u002Flaravel-sanctum-api-authentication\">Laravel Sanctum API authentication\u003C\u002Fa> once the request path is clear.\u003C\u002Fp>\n\n\u003Ch2>Why It Matters\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Faster debugging\u003C\u002Fstrong> — a 419 is CSRF middleware; a missing user is auth middleware; a blank 404 is routing. You stop guessing.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Safer changes\u003C\u002Fstrong> — you know whether a check belongs in a provider, global middleware, a route group, or the controller.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Correct boot order\u003C\u002Fstrong> — bindings belong in \u003Ccode>register()\u003C\u002Fcode>; using other services belongs in \u003Ccode>boot()\u003C\u002Fcode>. Mix those and you get circular resolve errors.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Predictable APIs\u003C\u002Fstrong> — SPA cookies, JSON exceptions, and CORS all attach at known layers of the same pipeline.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>How It Works\u003C\u002Fh2>\n\u003Cp>Conceptually Laravel does one thing: turn an \u003Ccode>Illuminate\\Http\\Request\u003C\u002Fcode> into an \u003Ccode>Illuminate\\Http\\Response\u003C\u002Fcode>. The layers in between are fixed.\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Front controller\u003C\u002Fstrong> — Apache\u002FNginx send every request to \u003Ccode>public\u002Findex.php\u003C\u002Fcode>. Composer autoload loads, then the app is created from \u003Ccode>bootstrap\u002Fapp.php\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Service providers\u003C\u002Fstrong> — every provider \u003Ccode>register()\u003C\u002Fcode>s bindings first. After that, every provider \u003Ccode>boot()\u003C\u002Fcode>s. Config, events, routes, and gates show up here.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>HTTP kernel\u003C\u002Fstrong> — Laravel 10 uses \u003Ccode>app\u002FHttp\u002FKernel.php\u003C\u002Fcode>. Laravel 11+ folds a lot of this into \u003Ccode>bootstrap\u002Fapp.php\u003C\u002Fcode>, but the job is the same: global middleware, then group middleware (\u003Ccode>web\u003C\u002Fcode> \u002F \u003Ccode>api\u003C\u002Fcode>), then route middleware.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Router\u003C\u002Fstrong> — method + URI match a route. Route model binding runs. If nothing matches, you get a 404 before any controller code.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Controller \u002F closure\u003C\u002Fstrong> — your app logic. Return a view, JSON, redirect, or a stream. Laravel wraps that return value into a Response.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Outbound middleware + terminate\u003C\u002Fstrong> — the response walks back through middleware. Then \u003Ccode>terminate()\u003C\u002Fcode> hooks run (session persist, logging) after the response is sent.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Artisan is a sibling path: \u003Ccode>artisan\u003C\u002Fcode> boots the same app, then the Console kernel dispatches a command. No HTTP middleware unless you fake a request.\u003C\u002Fp>\n\n\u003Ch2>Step-by-Step Guide\u003C\u002Fh2>\n\u003Cp>Walk a real \u003Ccode>POST \u002Flogin\u003C\u002Fcode> through the stack. Names differ slightly between Laravel 10 and 11; the order does not.\u003C\u002Fp>\n\n\u003Ch3>Step 1: Hit the front controller\u003C\u002Fh3>\n\u003Cp>\u003Ccode>public\u002Findex.php\u003C\u002Fcode> is the only public PHP entry. It requires Composer autoload, creates the application, then asks the HTTP kernel to handle the request.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F\u002F public\u002Findex.php (shape, not a copy-paste of every Laravel version)\nrequire __DIR__.'\u002F..\u002Fvendor\u002Fautoload.php';\n$app = require_once __DIR__.'\u002F..\u002Fbootstrap\u002Fapp.php';\n$kernel = $app-&gt;make(Illuminate\\Contracts\\Http\\Kernel::class);\n$response = $kernel-&gt;handle($request = Illuminate\\Http\\Request::capture());\n$response-&gt;send();\n$kernel-&gt;terminate($request, $response);\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>If this file is missing from the web root, you get directory listings or “index of \u002F” — not a Laravel 404.\u003C\u002Fp>\n\n\u003Ch3>Step 2: Bootstrap the application\u003C\u002Fh3>\n\u003Cp>\u003Ccode>bootstrap\u002Fapp.php\u003C\u002Fcode> returns the \u003Ccode>Application\u003C\u002Fcode> container. Laravel 11+ also registers routing, middleware, and exception handling here:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>return Application::configure(basePath: dirname(__DIR__))\n    -&gt;withRouting(\n        web: __DIR__.'\u002F..\u002Froutes\u002Fweb.php',\n        api: __DIR__.'\u002F..\u002Froutes\u002Fapi.php',\n        commands: __DIR__.'\u002F..\u002Froutes\u002Fconsole.php',\n        health: '\u002Fup',\n    )\n    -&gt;withMiddleware(function (Middleware $middleware) {\n        \u002F\u002F\n    })\n    -&gt;withExceptions(function (Exceptions $exceptions) {\n        \u002F\u002F\n    })-&gt;create();\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Until this returns, facades and \u003Ccode>app()\u003C\u002Fcode> helpers are not fully available. Don’t put business logic in \u003Ccode>index.php\u003C\u002Fcode>.\u003C\u002Fp>\n\n\u003Ch3>Step 3: Register, then boot service providers\u003C\u002Fh3>\n\u003Cp>Listed in \u003Ccode>bootstrap\u002Fproviders.php\u003C\u002Fcode> (Laravel 11+) or \u003Ccode>config\u002Fapp.php\u003C\u002Fcode> (older). Order:\u003C\u002Fp>\n\u003Col>\n\u003Cli>All \u003Ccode>register()\u003C\u002Fcode> methods — bind interfaces, merge config. Do not resolve other providers’ services here if you can avoid it.\u003C\u002Fli>\n\u003Cli>All \u003Ccode>boot()\u003C\u002Fcode> methods — routes, view composers, gates, event listeners. The container is ready.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cpre>\u003Ccode>class AppServiceProvider extends ServiceProvider\n{\n    public function register(): void\n    {\n        $this-&gt;app-&gt;singleton(InvoiceNumberGenerator::class);\n    }\n\n    public function boot(): void\n    {\n        Gate::policy(Document::class, DocumentPolicy::class);\n    }\n}\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Deferred providers only boot when something actually resolves them. That’s why a listener “sometimes doesn’t exist” until a related class is used.\u003C\u002Fp>\n\n\u003Ch3>Step 4: Run the HTTP kernel and middleware\u003C\u002Fh3>\n\u003Cp>Kernel pipeline (mental model):\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Global\u003C\u002Fstrong> — TrustProxies, HandleCors, PreventRequestsDuringMaintenance, TrimStrings\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Group\u003C\u002Fstrong> — \u003Ccode>web\u003C\u002Fcode>: cookies, session, CSRF, SubstituteBindings. \u003Ccode>api\u003C\u002Fcode>: throttle, bindings, Sanctum stateful check if you added it\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Route\u003C\u002Fstrong> — \u003Ccode>auth\u003C\u002Fcode>, \u003Ccode>auth:sanctum\u003C\u002Fcode>, \u003Ccode>verified\u003C\u002Fcode>, custom aliases\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Middleware can abort early. CSRF on a \u003Ccode>web\u003C\u002Fcode> POST without a token returns 419 \u003Cem>before\u003C\u002Fem> the controller. Auth middleware returns 401\u002Fredirect before your \u003Ccode>store()\u003C\u002Fcode> method.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Route::middleware('auth')-&gt;group(function () {\n    Route::post('\u002Fdocuments', [DocumentController::class, 'store']);\n});\u003C\u002Fcode>\u003C\u002Fpre>\n\n\u003Ch3>Step 5: Match the route and resolve the controller\u003C\u002Fh3>\n\u003Cp>Router looks at verb + URI + domain. Then:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Implicit \u002F explicit route model binding\u003C\u002Fli>\n\u003Cli>Form Request authorization + validation (\u003Ccode>StoreDocumentRequest\u003C\u002Fcode>)\u003C\u002Fli>\n\u003Cli>Controller method \u002F invokable \u002F closure\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cpre>\u003Ccode>public function store(StoreDocumentRequest $request)\n{\n    $document = Document::create($request-&gt;validated());\n    return redirect()-&gt;route('documents.show', $document);\n}\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>If validation fails, Laravel never enters the method. That’s still the lifecycle — Form Request is middleware-adjacent, not “controller code.”\u003C\u002Fp>\n\n\u003Ch3>Step 6: Send the response and terminate\u003C\u002Fh3>\n\u003Cp>Whatever you return (array, model, view, redirect) is converted to a Response. Outbound middleware can still change headers (CORS, cookies). Then \u003Ccode>send()\u003C\u002Fcode> writes to the client, and \u003Ccode>terminate()\u003C\u002Fcode> runs: session write, queued cookies, some loggers.\u003C\u002Fp>\n\u003Cp>Work that must finish after the browser already has the page belongs in \u003Ccode>dispatch()->afterResponse()\u003C\u002Fcode> or a queued job—not in the controller after \u003Ccode>return\u003C\u002Fcode>, because \u003Ccode>return\u003C\u002Fcode> already ended your method. Terminable middleware is the official “after send” hook.\u003C\u002Fp>\n\n\u003Ch2>Real-World Example\u003C\u002Fh2>\n\u003Cp>A Nuxt SPA posts login to Laravel on \u003Ccode>api.example.com\u003C\u002Fcode>. The user sees 419, then CORS errors, then an empty user object. Three bugs, three layers.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>419:\u003C\u002Fstrong> login route sat in \u003Ccode>web\u003C\u002Fcode> without \u003Ccode>\u002Fsanctum\u002Fcsrf-cookie\u003C\u002Fcode>. CSRF middleware ran; controller never did.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>CORS:\u003C\u002Fstrong> \u003Ccode>HandleCors\u003C\u002Fcode> is global, but \u003Ccode>supports_credentials\u003C\u002Fcode> was false and the origin wasn’t allowed. Browser blocked the response after Laravel had already succeeded.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Empty user:\u003C\u002Fstrong> \u003Ccode>\u002Fapi\u002Fuser\u003C\u002Fcode> used \u003Ccode>auth:sanctum\u003C\u002Fcode>, but the SPA didn’t send cookies (\u003Ccode>withCredentials\u003C\u002Fcode>). Sanctum ran, found no session and no Bearer token, returned 401. Frontend mapped that to \u003Ccode>{}\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>Once the team drew the lifecycle on a whiteboard—bootstrap → CORS → stateful Sanctum → CSRF → session → route → controller—the fixes were one-liners, not a rewrite. Same pattern I use on Laravel + Nuxt work like \u003Ca href=\"\u002F\">Complere eQMS\u003C\u002Fa>: locate the layer, then change that layer only.\u003C\u002Fp>\n\n\u003Ch2>Pros &amp; Cons\u003C\u002Fh2>\n\u003Ch3>Advantages\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>One documented pipeline for every HTTP request\u003C\u002Fli>\n\u003Cli>Middleware and providers give clear extension points\u003C\u002Fli>\n\u003Cli>Same bootstrap for HTTP and artisan, so config\u002Fbindings stay consistent\u003C\u002Fli>\n\u003Cli>Early abort (CSRF, auth, maintenance) keeps controllers thin\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Disadvantages\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Laravel 10 Kernel vs Laravel 11 \u003Ccode>bootstrap\u002Fapp.php\u003C\u002Fcode> makes tutorials mismatch your repo\u003C\u002Fli>\n\u003Cli>Too much logic in \u003Ccode>AppServiceProvider::boot()\u003C\u002Fcode> slows every request\u003C\u002Fli>\n\u003Cli>Middleware order is easy to get wrong (CORS vs cookies vs Sanctum)\u003C\u002Fli>\n\u003Cli>Magic (facades, implicit binding) hides the pipeline until something breaks\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>Best Practices\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Bind in \u003Ccode>register()\u003C\u002Fcode>, use in \u003Ccode>boot()\u003C\u002Fcode>\u003C\u002Fstrong> — don’t resolve sibling services too early.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Put request checks in middleware or Form Requests\u003C\u002Fstrong>, not in a 40-line controller constructor.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Keep \u003Ccode>web\u003C\u002Fcode> and \u003Ccode>api\u003C\u002Fcode> groups honest\u003C\u002Fstrong> — sessions\u002FCSRF on cookie SPAs; tokens on mobile. Mixing both on one route is how Sanctum “randomly” fails.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Log or dump at the layer you suspect\u003C\u002Fstrong> — \u003Ccode>dd()\u003C\u002Fcode> in a controller is useless if middleware already returned 419.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Don’t boot heavy work globally\u003C\u002Fstrong> — third-party SDKs belong in deferred providers or the class that needs them.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Treat terminate as after-response\u003C\u002Fstrong> — don’t assume the client waited for your extra queries.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>Common Mistakes\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Calling other services in \u003Ccode>register()\u003C\u002Fcode>\u003C\u002Fstrong> → Fix: move that code to \u003Ccode>boot()\u003C\u002Fcode> or a deferred callback.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Debugging a 419 inside the controller\u003C\u002Fstrong> → Fix: inspect CSRF \u002F session middleware and the \u003Ccode>web\u003C\u002Fcode> group; the controller never ran.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>API routes accidentally using the \u003Ccode>web\u003C\u002Fcode> stack\u003C\u002Fstrong> → Fix: confirm \u003Ccode>routes\u002Fapi.php\u003C\u002Fcode> prefix and middleware in \u003Ccode>bootstrap\u002Fapp.php\u003C\u002Fcode> or \u003Ccode>RouteServiceProvider\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Custom middleware registered but not attached\u003C\u002Fstrong> → Fix: alias it and add it to the route or group. Registration ≠ execution.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Assuming \u003Ccode>dd($request-&gt;user())\u003C\u002Fcode> works before \u003Ccode>auth\u003C\u002Fcode> middleware\u003C\u002Fstrong> → Fix: user is resolved when auth middleware (or guard) runs, not at bootstrap.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Heavy queries in a service provider \u003Ccode>boot()\u003C\u002Fcode>\u003C\u002Fstrong> → Fix: lazy-load; providers run on every request, including health checks.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>Frequently Asked Questions\u003C\u002Fh2>\n\u003Ch3>What is the Laravel lifecycle?\u003C\u002Fh3>\n\u003Cp>It is the sequence Laravel follows to handle a request: load autoload, create the app, boot service providers, run HTTP kernel middleware, match a route, execute a controller, send a response, then terminate. Artisan uses the same bootstrap with the console kernel.\u003C\u002Fp>\n\n\u003Ch3>How do I trace a Laravel request step by step?\u003C\u002Fh3>\n\u003Cp>Start at \u003Ccode>public\u002Findex.php\u003C\u002Fcode>, then \u003Ccode>bootstrap\u002Fapp.php\u003C\u002Fcode>, providers, middleware groups, \u003Ccode>routes\u002Fweb.php\u003C\u002Fcode> or \u003Ccode>routes\u002Fapi.php\u003C\u002Fcode>, then the controller. Laravel Debugbar, Telescope, or a temporary log in middleware will show where the request died.\u003C\u002Fp>\n\n\u003Ch3>Laravel lifecycle vs middleware — what’s the difference?\u003C\u002Fh3>\n\u003Cp>The lifecycle is the whole path. Middleware is one layer inside it, sitting between the kernel and the router\u002Fcontroller. Middleware can stop the lifecycle early or change the response on the way out.\u003C\u002Fp>\n\n\u003Ch3>Is learning the Laravel lifecycle worth it?\u003C\u002Fh3>\n\u003Cp>Yes if you debug auth, CSRF, sessions, or packages. You don’t need to memorize Illuminate source. You do need the order: providers → middleware → route → controller → terminate.\u003C\u002Fp>\n\n\u003Ch3>Where do service providers run in the lifecycle?\u003C\u002Fh3>\n\u003Cp>After the application is created and before the kernel handles the request. All \u003Ccode>register()\u003C\u002Fcode> methods run first, then all \u003Ccode>boot()\u003C\u002Fcode> methods. Route files are typically loaded from a provider or \u003Ccode>withRouting()\u003C\u002Fcode> during that boot phase.\u003C\u002Fp>\n\n\u003Ch2>Summary\u003C\u002Fh2>\n\u003Cp>Laravel lifecycle is not abstract theory. It is the ordered list of files and layers that turn a request into a response: \u003Ccode>index.php\u003C\u002Fcode>, application bootstrap, service providers, kernel middleware, routing, controller, then terminate.\u003C\u002Fp>\n\u003Cp>Put bindings in \u003Ccode>register()\u003C\u002Fcode>, app wiring in \u003Ccode>boot()\u003C\u002Fcode>, cross-cutting checks in middleware, and business rules in controllers or actions. When something fails, ask which layer ran last—not which tutorial you copied.\u003C\u002Fp>\n\u003Cp>Next: pick one failing request in your app, write the six steps beside it, and fix only that layer. If you want this mapped onto a Laravel + Nuxt stack, \u003Ca href=\"\u002Fabout\">get in touch\u003C\u002Fa>.\u003C\u002Fp>\n\n\u003Ch2>Key Takeaways\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Every HTTP request enters through \u003Ccode>public\u002Findex.php\u003C\u002Fcode> and leaves as a Response plus \u003Ccode>terminate()\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>Providers: \u003Ccode>register()\u003C\u002Fcode> then \u003Ccode>boot()\u003C\u002Fcode>. Don’t reverse that.\u003C\u002Fli>\n\u003Cli>Middleware can abort before your controller — 419, 401, 403 usually mean this.\u003C\u002Fli>\n\u003Cli>Router match + Form Requests sit between middleware and controller code.\u003C\u002Fli>\n\u003Cli>Debug by layer (bootstrap, middleware, route, controller), not by stacking more dumps in the action.\u003C\u002Fli>\n\u003C\u002Ful>","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1786777544862-khxf92.webp","Laravel Lifecycle: Request to Response","Trace the Laravel lifecycle from bootstrap to response: service providers, middleware, routing, controllers, and where to debug 404s and 419s.","",[19,20,21,22,23],"Laravel","PHP","Request Lifecycle","Middleware","Backend","published","2026-08-15T07:15:13.877+00:00",11,null,"2026-08-15T07:05:53.808352+00:00","2026-08-15T07:15:13.978037+00:00",[],{"variant":32,"profile":37,"heroStats":50,"aboutParagraphs":54,"aboutPillars":61,"aboutFacts":74,"skillCategories":87,"experiences":128,"education":155,"projects":174,"languages":244,"interests":247},{"id":33,"slug":34,"label":35,"is_active":36,"sort_order":4},"481b2725-e0f6-43df-beea-937ec806a438","full-stack-developer","Full Stack Developer",true,{"name":38,"title":39,"tagline":39,"photo_url":40,"summary":41,"email":42,"phone":17,"location":43,"linkedin":44,"github":45,"instagram":46,"hero_headline":47,"hero_headline_accent":48,"hero_subheadline":49},"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.",[51],{"value":52,"label":53},"3.5+","Yrs Development",[55,57,59],{"html":56},"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":58},"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":60},"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.",[62,66,70],{"icon":63,"label":64,"description":65},"lucide:code-2","Build","Scalable, clean web apps",{"icon":67,"label":68,"description":69},"lucide:trending-up","Grow","Marketing-driven results",{"icon":71,"label":72,"description":73},"lucide:shield-check","Ship","Reliable, compliant systems",[75,79,83],{"icon":76,"label":77,"value":78},"lucide:settings","Core Stack","Laravel · Nuxt · Vue · MySQL",{"icon":80,"label":81,"value":82},"lucide:building-2","Currently","Complibued — eQMS Platform",{"icon":84,"label":85,"value":86},"lucide:map-pin","Availability","Open to opportunities",[88,101,112,123],{"title":89,"icon":90,"color":91,"show_on_home":36,"show_on_resume":36,"skills":92},"Backend Development","lucide:database","from-gold-soft to-gold-deep",[19,20,93,94,95,96,97,98,99,100],"Supabase (BaaS)","MySQL","REST APIs","Git","Docker","Redis","GitHub Actions","Cloudflare",{"title":102,"icon":103,"color":91,"show_on_home":36,"show_on_resume":104,"skills":105},"Frontend Development","lucide:code",false,[106,107,108,109,110,111],"Nuxt.js","Vue.js","React","TypeScript","Tailwind CSS","JavaScript",{"title":113,"icon":114,"color":91,"show_on_home":36,"show_on_resume":104,"skills":115},"AI & Automation","lucide:zap",[116,117,118,119,120,121,122],"Prompt Engineering","ChatGPT & Claude","Google Gemini","AI Grok","GitHub Copilot","AI Content Strategy","Workflow Automation",{"title":124,"icon":125,"color":91,"show_on_home":36,"show_on_resume":36,"skills":126},"Development","lucide:wrench",[19,20,107,106,111,109,110,95,94,127],"Git & GitHub",[129],{"role":35,"company":130,"note":131,"period":132,"description":133,"stack":134,"color":91,"icon":135,"points":136},"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",[137,140,142,144,146,149,151,153],{"text":138,"surface":139},"Developing and maintaining a pharma-focused eQMS platform using Laravel and Nuxt.js.","resume",{"text":141,"surface":139},"Built compliance-critical modules: Document Control, Training (LMS), Event Handling, CAPA, Change Control (CR), Audit, and Risk Assessment (RA).",{"text":143,"surface":139},"Implemented approval workflows, version control, and immutable audit trails aligned to 21 CFR Part 11.",{"text":145,"surface":139},"Collaborated with QA teams to meet pharmaceutical compliance standards.",{"text":147,"surface":148},"Built Document Control & LMS (training) modules","home",{"text":150,"surface":148},"Implemented CAPA and Event management workflows",{"text":152,"surface":148},"Developed Change Control (CR) with impact-assessed approvals",{"text":154,"surface":148},"Delivered Audit & Risk Assessment (RA) modules with audit trails",[156,161,165,170],{"degree":157,"school":158,"period":159,"score":160},"M.Sc. (Computer Science)","MDS University, Ajmer","2023 – 2025","73%",{"degree":162,"school":158,"period":163,"score":164},"BCA","2020 – 2023","71%",{"degree":166,"school":167,"period":168,"score":169},"Senior Secondary (12th)","RBSE, Ajmer","2018 – 2019","68.80%",{"degree":171,"school":167,"period":172,"score":173},"Secondary (10th)","2016 – 2017","48.75%",[175,192,209],{"title":176,"slug":177,"description":178,"why":179,"category":180,"image":181,"emoji":182,"link":183,"is_active":36,"stack":184,"features":186,"metrics":191},"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",[107,185,94,110,109],"Supabase",[187,188,189,190],"Stock Tracking","Order Management","User Authentication","Reporting & Analytics",[],{"title":193,"slug":194,"description":195,"why":196,"category":197,"image":198,"emoji":199,"link":200,"is_active":36,"stack":201,"features":203,"metrics":208},"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",[107,202,185,110,109],"WebRTC",[204,205,206,207],"Peer-to-Peer Video","Random Matchmaking","Realtime Signaling","No Sign-up Required",[],{"title":210,"slug":211,"description":212,"why":213,"category":214,"image":198,"emoji":215,"link":216,"is_active":36,"stack":217,"features":225,"metrics":234},"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",[218,219,220,221,110,109,94,222,223,224,97],"Laravel 12","Nuxt 4","Vue 3","Vuetify 3","stancl\u002Ftenancy","Laravel Sanctum","Spatie Permission",[226,227,228,229,230,231,232,233],"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)",[235,238,241],{"value":236,"label":237},"1","Product platform",{"value":239,"label":240},"7+","Core modules",{"value":242,"label":243},"MT","Multi-tenant",[245,246],"Hindi","English",[248,249,250],"Web Development","Video Content","New Tools & Tech",[252,267,284,300,313,327,339,351,364,377,388,399,411,413,427,438,448,457,468,481,493,502,513,526],{"id":253,"title":254,"slug":255,"excerpt":256,"cover_image":257,"tags":258,"published_at":264,"updated_at":265,"view_count":266},"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",[259,260,261,262,263,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":268,"title":269,"slug":270,"excerpt":271,"cover_image":272,"tags":273,"published_at":281,"updated_at":282,"view_count":283},"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",[274,275,276,260,6,277,278,279,280],"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":285,"title":286,"slug":287,"excerpt":288,"cover_image":289,"tags":290,"published_at":297,"updated_at":298,"view_count":299},"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,291,292,293,294,295,296],"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":301,"title":302,"slug":303,"excerpt":304,"cover_image":305,"tags":306,"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",[295,307,308,109,309],"ImageKit","Vue","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":283},"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",[19,358,359,20,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",[19,371,372,373,20],"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":387},"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,371,20,384,360],"ORM","2026-08-19T07:03:17.721+00:00","2026-08-20T04:19:08.829027+00:00",18,{"id":389,"title":390,"slug":391,"excerpt":392,"cover_image":393,"tags":394,"published_at":397,"updated_at":398,"view_count":283},"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,395,371,20,396],"Database","Transactions","2026-08-19T04:44:00.327+00:00","2026-08-19T05:14:18.190197+00:00",{"id":400,"title":401,"slug":402,"excerpt":403,"cover_image":404,"tags":405,"published_at":409,"updated_at":410,"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",[19,406,20,407,408],"Auditing","Security","Activity Log","2026-08-15T21:24:32.135+00:00","2026-08-15T21:24:32.194447+00:00",{"id":9,"title":10,"slug":11,"excerpt":12,"cover_image":14,"tags":412,"published_at":25,"updated_at":29,"view_count":26},[19,20,21,22,23],{"id":414,"title":415,"slug":416,"excerpt":417,"cover_image":418,"tags":419,"published_at":425,"updated_at":426,"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",[420,421,422,423,424],"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":428,"title":429,"slug":430,"excerpt":431,"cover_image":432,"tags":433,"published_at":436,"updated_at":437,"view_count":387},"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",[295,22,434,435,308],"SSR","Auth","2026-08-05T04:09:38.347+00:00","2026-08-05T04:09:38.496803+00:00",{"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",[295,308,434,445,111],"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",[19,291,296,20,294,407],"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":387},"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,291,464,296,20,465,294],"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",[19,475,23,476,477,20,109,248],"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",[109,111,248,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",[111,248,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":387},"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,291,509,510,294],"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",[19,20,520,521,23,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",[19,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"]