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)

Understanding Vue plugins

When making a new Vue app with the help of the Vue CLI from the command line, we use the vue create command. We are then taken through a number of steps and prompts that we need to choose, so that our app is properly configured. What we are actually doing, among other things, is choosing which Vue plugins will end up being used in our app.

Plugins are a way to add functionality to our Vue projects. Some plugins are more complex than others; they sometimes have their own prompts that appear during installation. Our Vue app's configurations, that is, the underlying code, will reflect our choices. The way our app is set up will be based on the answers we provide to these installation prompts.

All the official npm packages of a project are scoped with the @ symbol, followed by the project name. Thus, official Vue plugins, built by the Vue maintainers...