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)

What ESLint is, and how to configure it on its own

In this chapter, we will discuss the role of ESLint. ESLint has to do with code quality. When you work on a team, every team member will bring their own little quirks and ideas on the best way to write JavaScript. Even if your team has some clear-cut rules on specific coding styles and how to write your code, how do you guarantee that each team member will follow the rules? How do you make sure that they deliver consistent code quality? We are human after all, which means that we all have those days when we do our best, but simply forget about one little thing that we had to pay attention to.

Given a long enough period of time, our team will begin producing stylistically inconsistent code. The next thing that happens is, everyone in the team starts perceiving the JavaScript style guide as a suggestion, not something that you should...