Chapter 1: Introduction to Vite

Recently, there has been considerable conversation at my workplace regarding our build procedures and overall development setup. Vite has surfaced as a promising new tool that we might incorporate. Prior to this, I was unaware of Vite's functionalities, so I decided to investigate further.

Vite describes itself as a tool for "Next Generation Frontend Tooling," which certainly piqued my interest.

As I delved deeper, I stumbled upon insightful podcast episodes featuring its creator, Evan You, including discussions like A Deep-Dive on Vite and A Vite Demo.

Vite serves two primary purposes:

• A development server
• A build tool

The development server aspect is particularly captivating. In a conventional local development setup, developers usually must bundle their applications before viewing them in a browser. Older browsers, which lack support for ES modules, require all JavaScript code and its dependencies to be consolidated into a single file. This bundling process often leads to prolonged startup times, especially for larger applications. Vite capitalizes on modern browsers' inherent capability to handle ES modules, allowing developers to bypass pre-compilation. Consequently, the browser itself acts as a substitute for the bundler, requesting only the code necessary for the current view.

I plan to explore the build tool functionality in further detail in an upcoming post as I continue my research.

Section 1.1: Monorepos and Vite

In my current workplace, we manage multiple monorepos. I recognize the importance of conducting thorough research on how to best implement Vite in this context. I have a hunch that this will evolve into an ongoing exploration, potentially leading us to consolidate everything into a single monorepo for simplicity. The concept of maintaining multiple monorepos has always seemed inefficient to me.

Subsection 1.1.1: Image Placeholder

Chapter 2: Finding Balance

Unfortunately, I have made no progress in golf due to a busy work schedule and my current getaway. I almost packed my laptop but ultimately decided against it. Taking a break from screens is essential, especially given how dominated my life is by technology. It’s good for my eyes to have a rest (even as I type this while squinting at my phone). Regular updates related to golf will resume in a few weeks once I return to my normal routine. My lack of golf practice lately has also diminished my motivation to improve in this area. Balancing coding from 9 to 6 (interrupted by meetings) with evening activities can be challenging, and I need to find the right equilibrium.