It took a lot of time just to adjust with the file directory and to switch from react to vite. I built a local Node.js server using Express to securely handle my API requests in the future. For now, this backend is loaded with mock data and simulated network delays to perfectly mimic live telemetry without needing actual credentials yet. On the frontend, I established a strict CSS Grid layout. Early on, a manually created, empty package file caused a JSON parsing crash on the backend, which I quickly resolved by letting Node generate a properly formatted blueprint. On the frontend, I initially faced turbulence by applying a standard backend initialization, which left me without a bundler to actually run the React code. I quickly pivoted, cleared the deck, and installed Vite system to compile and serve the user interface. My final challenge was a strict lesson in mapping. Vite is highly case-sensitive, and it threw a red screen of import errors because the folder names (like “Components” with a capital C) didn’t perfectly match the lowercase names in my code. By simply aligning the map and renaming the files in the sidebar to match the exact casing, Vite’s hot module replacement instantly caught the changes and the website was running in the browser.