Book Image

Vue CLI 3 Quick Start Guide

By : Ajdin Imsirovic
Book Image

Vue CLI 3 Quick Start Guide

By: Ajdin Imsirovic

Overview of this book

The sprawling landscape of various tools in JavaScript web development is becoming overwhelming. This book will show you how Vue CLI 3 can help you take back control of the tool chain. To that end, we'll begin by configuring webpack, utilizing HMR, and using single-file .vue components. We'll also use SCSS, ECMAScript, and TypeScript. We'll unit test with Jest and perform E2E testing with Cypress. This book will show you how to configure Vue CLI as your default way of building Vue projects. You'll discover the reasons behind using webpack, babel, eslint, and other modern JavaScript toolchain technologies. You'll learn about the inner workings of each through the lens of Vue CLI 3. We'll explore the extendibility of Vue CLI with the built-in settings, and various core and third-party plugins. Vue CLI helps you work with Vue components, routers, directives, and services in the Vue ecosystem. While learning these concepts, you'll examine the evolution of JavaScript. You'll learn about use of npm, IIFEs, modules in JavaScript, Common.js modules, task runners, npm scripts, module bundlers, and webpack. You'll get familiar with the reasons why Vue CLI 3 is set up the way it is. You'll also learn to perform linting with ESLint and Prettier. Towards the end, we'll introduce you to working with styles and SCSS. Finally, we'll show you how to deploy your very own Vue project on Github Pages.
Table of Contents (10 chapters)

Test-driven development in Vue CLI 3

TDD is development based on the idea of the red-green-refactor cycle. Similar to what we've seen in the preceding code, we first write our code so that our test fails. Next, we write our code so that our test passes, and finally we refactor our code.

For each new feature in our apps, we repeat the same process. This is essentially what TDD is.

TDD is just a streamlined way of writing any application in any language or framework. It streamlines our work by allowing us to split our entire project into testable, clearly separated chunks of functionality.

The red-green-refactor approach is clearly visible in our output on the Project tasks page too. If we write a failing test, we'll see a red background on the word fail. It we write a passing test, we'll see a green background on the work pass.

Through the rest of this chapter, we...