Having Trouble Getting Your Website to Work as Expected?

The development server renders your code entirely in the browser using client side scripts. A production build often generates the initial HTML on the server before sending it to the user. If your component uses browser specific objects like the window variable during this first render, the server crashes. The resulting HTML does not match what the client expects to see. Moving this browser logic into a dedicated use effect hook prevents the mismatch from occurring.

Browsers protect users by sending an automated preflight options request before transmitting any complex JSON data across different domains. Your backend server must explicitly listen for this options request on the exact target route. The server responds with headers confirming that the post method and custom content types are permitted. Without this specific preflight response, the browser blocks the actual payload and throws a network error in the console. Adding an explicit options route handler fixes the blocked transmission and satisfies the browser security protocol.

Storing the fetched network data in a standard local variable does not signal the rendering engine that the interface needs to change. Modern frontend frameworks track specific memory references to determine exactly when a visual update is required. You must pass the parsed JSON response into the designated state setter function provided by your chosen framework. This specific function call queues a new render cycle and injects the fresh data into your interface structure. The component finally paints the screen with the fetched network payload.

Storing the authentication token in standard memory means it vanishes the moment the browser tab reloads or closes. You must save the encoded string into an HTTP only cookie rather than local storage. Local storage is accessible to JavaScript running on the page, which means any cross site scripting vulnerability exposes every stored token immediately. An HTTP only cookie cannot be read by client side scripts, which satisfies the security requirements most university modules now enforce explicitly.

Desktop layouts built with fixed pixel widths force interface elements to maintain their exact dimensions regardless of the physical screen size. When viewed on a mobile device, these rigid containers overflow the visible viewport and cause frustrating horizontal scrolling. Replacing those fixed pixel values with relative percentages or viewport units allows the layout containers to shrink naturally. Adding media queries at specific breakpoints lets you stack multi column designs into single columns for much narrower mobile screens. This approach satisfies standard responsive design criteria.

Opening a brand new database connection for every single incoming API request rapidly consumes all available memory on the backend database server. You should create one single connection pool object when your Node application first starts up. Each individual route handler requests a temporary client from this central pool to execute its specific SQL query. You must explicitly release that client back to the pool inside a finally block so other incoming requests can use it. This prevents concurrent requests from exhausting the available connections and returning timeout errors to every subsequent caller.

The working code demonstrates that you can write correct syntax and achieve the functional requirements outlined in the original assignment brief. The written report proves that you understand exactly why those specific libraries and data structures were chosen over other alternative options. A flawless web application built with a deeply flawed architecture often fails the module entirely under strict marking schemes. Instructors use the justification document to verify that the student actually engineered the solution rather than copying it from an open source repository. The report is where the academic reasoning is graded.