Book Image

Vue.js: Understanding its Tools and Ecosystem

By : Dave Berning
Book Image

Vue.js: Understanding its Tools and Ecosystem

By: Dave Berning

Overview of this book

Vue.js is one of the top three “go-to” JavaScript frameworks and is used by organizations such as Nintendo, NASA, and Expedia. This book is primarily focused on the ecosystem of Vue.js and its development tools. Understanding the basics of the technology behind the Vue.js ecosystem will improve your skills and make you a better problem solver. The book begins with a brief overview of Vue.js. You’ll learn to work your way through the Vue command line interface CLI 3, and use the Vue Router library to navigate between the different views of your application. As you advance through the topics, you’ll explore the use of DevTools to improve the quality of your applications and how to implement server-side rendering in your application through the Nuxt.js framework. Toward the end of the book, you’ll read about the future of Vue.js and its growing popularity. After reading this book, you’ll be able to create industry-grade applications using Vue.js and its tools.
Table of Contents (11 chapters)

Type Casting with TypeScript

Type casting is the practice of defining the function or code as best as you can. Below are some basic types that TypeScript checks for:

  • string: “TypeScript is awesome!”
  • number: 0, 1, 2, etc.
  • object: { language: “typescript” }
  • boolean: true or false
  • undefined: Data is not defined
  • void: Nothing
  • any: Literary any data type

Let’s annotate our alertMe() function using these types. To annotate an argument or function, you use the colon (:) followed by the type.

function alertMe(message: string): void {
  alert(message);
}

In this case, we are explicitly defining the message parameter as a string and nothing else. If you compile this function again using the tsc command, this time with the one instance of alertMe(). But this time, pass in a number instead. You will still receive the same error! At this point, TypeScript is no longer inferring the type; this type it’s explicitly stated.

You should have noticed something...