Chapter 1, Going Shopping with Vue.js, contains an introduction to Vue.js, to the terminology used through the book, and first basic examples.

Chapter 2, Fundamentals – Installing and Using, explains the behind the scenes of Vue.js, provides theoretical insights into the architectural pattern, touches nearly all the main Vue.js concepts, and bootstraps the applications that will be developed through the book.

Chapter 3, Components – Understanding and Using , goes deep into components and explains how to rewrite applications using a simple component system and single-file components.

Chapter 4, Reactivity – Binding Data to Your Application , contains a detailed explanations of the usage of data binding mechanisms in Vue.js.

Chapter 5, Vuex – Managing State in Your Application , contains detailed introduction to Vuex, a state management system for Vue.js, and explains how to use it in your application in order to achieve a nice, maintainable architecture.

Chapter 6, Plugins – Building Your House with Your Own Bricks , shows how to use plugins in Vue applications and explains how to use an existing plugin in an application and explains how to build our own plugin and then use it.

Chapter 7, Testing – Time to Test What We Have Done So Far, contains an introduction to the testing techniques that can be used in Vue applications to bring them to the needed level of quality. We tackle it by showing how to write unit tests and how to develop end-to-end tests for the applications in the book.

Chapter 8, Deploying – Time to Go Live!, shows how to bring your Vue application to the world, guaranteeing its quality with continuous integration tools. It explains how to connect a GitHub repository to the Travis continuous integration system and to the Heroku cloud deployment platform.

Chapter 9, What Is Next, wraps up everything that has been done so far and leaves the reader with the follow up steps.

Appendix, Solutions to Exercises, provides solutions to the exercises for first three chapters.

The requirements for this book are the following:

This book is for web developers or for people who want to become web developers. Whether you have just started to work with web technologies or you are already a guru of frameworks and languages in the vast ocean of web technologies, this book might show you something new in the world of reactive web applications. If you are a Vue developer and have used Vue 1.0, this book might be a useful guide for you to migrate to Vue 2.0, since all the examples of the book are based on Vue 2.0. Even if you are already using Vue 2.0, this book might be a nice exercise of building an application from scratch, applying all Vue and software engineering concepts and taking it to the deployment stage.

At least some technical background is required. If you can already write code in JavaScript, it is a huge plus.

In this book, you will find a number of text styles that distinguish between different kinds of information. Here are some examples of these styles and an explanation of their meaning.

Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "Your plugin must provide an install method."

A block of code is set as follows:

export default {
  components: {
    ShoppingListComponent,
    ShoppingListTitleComponent
  },
  computed: mapGetters({
    shoppinglists: 'getLists'
  })
}

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

export default {
  components: {
    ShoppingListComponent,
    ShoppingListTitleComponent
  },
  computed: mapGetters({
    shoppinglists: 'getLists'
  }),
  methods: mapActions(['populateShoppingLists']),
  store,
  mounted () {
    this.populateShoppingLists()
  }
}

Any command-line input or output is written as follows:

cd shopping-list
npm install vue-resource --save-dev

New terms and important words are shown in bold. Words that you see on the screen, for example, in menus or dialog boxes, appear in the text like this: "Check the Developer mode checkbox."

Feedback from our readers is always welcome. Let us know what you think about this book-what you liked or disliked. Reader feedback is important for us as it helps us develop titles that you will really get the most out of. To send us general feedback, simply e-mail [email protected], and mention the book's title in the subject of your message. If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide at www.packtpub.com/authors.

Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.