Navigation guards are the control points where a Vue application decides whether a route transition should proceed, be cancelled, or be redirected. They exist because navigation is not always safe: a user might be navigating to a page they are not authenticated for, or leaving a form with unsaved changes, or entering a route that…
A Vue application’s UI is rarely a single flat layer. A dashboard has a persistent sidebar and a main content area. A settings page has a navigation panel and a detail pane. A user profile has a header that stays while the tab content changes. Vue Router expresses these structures through three distinct mechanisms: nested…
A URL like /users/42 and a URL like /users/42?tab=posts are both requests for the same resource, but they carry different kinds of information. The 42 is part of the path—it identifies which user. The tab=posts is a query string—it describes how to display that user. Vue Router treats these two as distinct concepts with distinct…
Converting standard functions to arrow functions by hand is tedious. You miss a return. You forget to remove the curly braces. You mess up the this binding. I built a free tool that solves this. What it does: Use cases: Privacy:100% client-side. Nothing uploaded. Try it: tools.kandz.me/arrow-function-converter
A native addon is a compiled shared library—a .node file—that JavaScript can require() like any other module. It exists because some operations are either impossible or unacceptably slow in JavaScript: calling an operating system API that Node.js does not expose, wrapping an existing C or C++ library that would take years to port, or running…
A command-line tool is a program that a user invokes by name from a terminal, passes arguments and options to, and receives output from. Building one in Node.js is deceptively straightforward: create a JavaScript file with a shebang, map it to a command name in package.json, and install it globally. The difficulty is not in…
Node.js Single Executable Applications (SEA) is the runtime’s native answer to a problem that third-party tools like pkg and nexe spent years addressing: how do you ship a Node.js application to a machine that does not have Node.js installed? The approach is deceptively simple. You bundle your application into a single JavaScript file, generate a…
A CI/CD pipeline is the mechanism that turns a git push into a tested, built, and deployed application without manual intervention. The pipeline has three stages that run in sequence: continuous integration verifies that the code compiles and the tests pass, continuous delivery builds the deployable artifact, and continuous deployment pushes that artifact to the…
A Node.js process that ignores SIGTERM is a process that Docker kills after ten seconds. An orchestrator sends the signal, waits for the configured grace period, and then sends SIGKILL—which cannot be caught, cannot be handled, and gives the application no opportunity to finish what it was doing. The difference between a clean shutdown and…
The previous chapter covered the four decisions that shape a production Node.js image. This chapter goes deeper into the two that have the largest measurable impact: the multi-stage build structure that determines what ships, and the non-root execution model that determines what happens when something goes wrong. The size difference is not marginal. A single-stage…