Now we'll round off our study of Vue by giving you a list of resources that you can use to go further in your learning, plus some other useful tips.
|Objective:||To learn where to go to find further information on Vue, to continue your learning.|
Here's where you should go to learn more about Vue:
- Vue Docs — The main Vue site. Contains comprehensive documentation, including examples, cookbooks, and reference material. This is the best place to start learning Vue in depth.
- Vue GitHub Repo — The Vue code itself. This is where you can report issues and/or contribute directly to the Vue codebase. Studying the Vue source code can help you better understand how the framework works, and write better code.
- Vue Forum — The official forum for getting help with Vue.
- Vue CLI Docs — Documentation for the Vue CLI. This contains information on customizing and extending the output you are generating via the CLI.
- NuxtJS — NuxtJS is a Server-Side Vue Framework, with some architectural opinions that can be useful to creating maintainable applications, even if you don't use any of the Server Side Rendering features it provides. This site provides detailed documentation on using NuxtJS.
- Vue Mastery — A paid education platform that specializes in Vue, including some free lessons.
- Vue School — Another paid education platform specializing in Vue.
The Vue CLI also provides us with tools for preparing our app for publishing to the web. You can do this like so:
- If your local server is still running, end it by pressing Ctrl + C in the terminal.
- Next, run the
npm run build(or
yarn build) in the console.
This will create a new
dist directory containing all of your production ready files. To publish your site to the web, copy the contents of this folder to your hosting environment.
Note: The Vue CLI docs also include a specific guide on how to publish your app to many of the common hosting platforms.
Vue 2 support will end on December 31st, 2023 and the default Vue version for all CLI tools will be version 3 and above.
The Composition API works as an alternative to the property-based API where a
setup() function is used on the component. Only what you return from this function is available in your
<template>s. You are required to be explicit about "reactive" properties when using this API. Vue handles this for you using the Options API. This makes the new API typically considered a more advanced use case.
If you're upgrading from Vue 2, it's recommended you take a look at the Vue 3 migration guide.