{"id":28116,"date":"2022-03-03T09:00:01","date_gmt":"2022-03-03T09:00:01","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=28116"},"modified":"2022-12-23T06:48:18","modified_gmt":"2022-12-23T06:48:18","slug":"what-is-vue-js-and-how-it-works-an-overview-and-its-use-cases","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/what-is-vue-js-and-how-it-works-an-overview-and-its-use-cases\/","title":{"rendered":"What is vue.js and How it works? An Overview and Its Use Cases"},"content":{"rendered":"

History & Origin of vue.js<\/h3>\n

Vue. js was\u00a0created originally by a single person, Evan You, a former Google engineer who used to work on Angular.<\/b>\u00a0js and later on the Meteor framework<\/b>. After experimenting with a reactivity system that he thought was better than the one used in Angular.<\/p>\n

Vue.js was created originally by a single person, Evan You, a former Google engineer who used to work on Angular.js and later on the Meteor framework. After experimenting with a reactivity system that he thought was better than the one used in Angular.js, he decided to publish his first results in July 2013. Five years later, Vue.js is the third project on Github in number of stars and Evan holds one conference after the other around the world.<\/p>\n

\"\"<\/p>\n

Development team<\/h2>\n

The development of Vue and its ecosystem is guided by an international team of about thirty voluntary members. The team is spread all over the world, which helped to make the framework popular worldwide. Thus it is easy to have support no matter your timezone.<\/p>\n

What is vue.js?<\/h3>\n

Vue. js is a progressive framework for JavaScript used\u00a0to build web interfaces and one-page applications<\/b>. Not just for web interfaces, Vue. js is also used both for desktop and mobile app development with Electron framework.<\/p>\n

Vue\u00a0(pronounced \/vju\u02d0\/, like view)<\/em>\u00a0is a progressive framework for building user interfaces. Unlike other monolithic frameworks, Vue is designed from the ground up to be incrementally adoptable. The core library is focused on the view layer only, and is easy to pick up and integrate with other libraries or existing projects. On the other hand, Vue is also perfectly capable of powering sophisticated Single-Page Applications when used in combination with modern tooling and supporting libraries.<\/p>\n

How Vue.js works aka Vue.js architecture?<\/h3>\n

\"\"<\/p>\n

\n

What is architecture of VueJS?<\/strong><\/h3>\n<\/div>\n
\n
\n
\n
\n
\n
The name of the framework \u2013 Vue \u2013 is the same phonetically in English as view, and it corresponds to the\u00a0traditional Model-View-Controller (MVC) architecture<\/b>. Simply put, view is a UI of an application\/website, and the core library of Vue. js focuses the view layer by default.<\/span><\/span><\/div>\n
In its current form, Vue.js, developed by Evan You on a full-time basis, benefited by contributions from community members, and funded mainly by Patreon. Without the financial support of enterprises like Facebook (React) and Google (Angular), Vue still has achieved wide adoption on\u00a0Github<\/a>.<\/div>\n
\n

Community-Wide Standards for Predictability<\/h2>\n

So this begs the question, what kind of standards exist for the Vue.js community at large? I’d say that there are 4 sources of standards available.<\/p>\n

    \n
  1. The Vue.js style guide<\/a><\/li>\n
  2. The scaffolding generated by the Vue CLI<\/li>\n
  3. the official Vue.js libraries (found under Ecosystem > Official Projects on the Vue.js website)<\/li>\n
  4. and more loosely, the most popular component frameworks like Vuetify or Quasar<\/li>\n<\/ol>\n

    While some of these are more officially meant to be standards over others, I think they all provide the opportunity to have some common patterns between projects and developers resulting in more predictable codebases.<\/p>\n

    Official Libraries and Component Libraries<\/h3>\n

    Let’s start by talking about the standardization that official libraries and popular component libraries bring. While the primary purpose of such libraries is to bring functionality to the table, a side affect of this is that shared standards are adopted. If you use Vue Router, for instance, you’re not only benefiting from the functionality of the package itself, but you end up implementing routes in one project much the same way as you implement them in another project and much the same way as Vue.js developers all over the world implement them.<\/p>\n

    The Vuex library in fact embraces and touts this fact as a top feature calling itself a “state management\u00a0pattern<\/strong>\u00a0+ library”.<\/p>\n

    This may seem obvious, but there is a point to be made. If there is an existing popular or recommended solution for a problem in Vue.js (and even more so if it’s an official solution), I would think long and hard before using something else. I’m just as happy as the next guy, DIYing my own components, stores, etc but often times it really pays off in the long run to use the tried and true solution not just because of the functionality, test coverage, and documentation they offer but also because of the standardization they bring. (And in the world of JavaScript can’t we all just use a bit more standardization)<\/p>\n<\/div>\n

    \n

    How does VueJS work?<\/strong><\/h3>\n<\/div>\n
    \n
    \n
    \n
    \n
    \n
    VueJS focuses\u00a0on the view part of your application<\/b>. To do so, the framework is partly inspired by the MVVM architecture pattern. VueJS will link your DOM, the view part, with your view instance, the Model-View part. These two parts are linked by the data-binding system.<\/span><\/span><\/div>\n
    <\/div>\n
    \n
    \n

    How VueJS is structured?<\/strong><\/h3>\n<\/div>\n
    \n
    \n
    \n
    \n
    \n
    A Vue application consists of a root Vue instance created with new Vue or createApp function(s),\u00a0optionally organized into a tree of nested, reusable components<\/b>. Creating a new Vue instance generally means an instruction for the Vue application to render a component, generally, it is the App component.<\/span><\/span>08-Mar-2021<\/span><\/div>\n
    \"\"<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
    Creating a new Vue instance generally means an instruction for the Vue application to render a component, generally, it is the App component. It doesn\u2019t mean that our application will consist of a single app component but the\u00a0App<\/em>\u00a0component will be the root component consisting of other components as child components.<\/div>\n
    <\/div>\n
    Creating Vue instance in Version 2<\/strong><\/div>\n
    \n
    \n
    <\/div>\n
      \n
    1. var<\/span>\u00a0vm\u00a0=\u00a0new<\/span>\u00a0Vue({<\/li>\n
    2. \u00a0\u00a0\u00a0\/\/\u00a0options\u00a0\u00a0<\/span><\/li>\n
    3. })<\/li>\n<\/ol>\n<\/div>\n<\/div>\n
      Here variable vm is a short notation for ViewModel. There are various ways in which we can pass options while creating a Vue instance so that we can have the desired behavior of our application. Referring to Vue\u2019s official site, Vue was inspired by the MVVM pattern.<\/div>\n
      <\/div>\n

      What is MVVM?<\/h2>\n
      <\/div>\n
      Model\u2013View\u2013ViewModel (MVVM) is a software architectural pattern that facilitates the separation of the development of the graphical user interface (the view) \u2013 be it via a markup language or GUI code \u2013 from the development of the business logic or back-end logic (the model) so that the view is not dependent on any specific model platform. The view model of MVVM is a value converter, meaning the view model is responsible for exposing (converting) the data objects from the model in such a way that objects are easily managed and presented.\u00a0Source: Wikipedia<\/div>\n
      <\/div>\n
      Creating Vue instance in Version 3<\/strong><\/div>\n
      \n
      \n
      <\/div>\n
        \n
      1. const<\/span>\u00a0app\u00a0=\u00a0Vue.createApp({<\/li>\n
      2. \u00a0\u00a0\u00a0\/*\u00a0options\u00a0*\/<\/span><\/li>\n
      3. })<\/li>\n<\/ol>\n<\/div>\n<\/div>\n
        <\/div>\n
        As we are already aware that to create a Vue instance in Vue 3 we use the function createApp, where we can register \u201cglobals\u201d that can be used by the rest of the components in our application.<\/div>\n
        <\/div>\n

        What are components in Vue.js?<\/h2>\n
        <\/div>\n
        \n
        A component is not generally a Vue instance but components are reusable Vue instances to which we can provide names. Generally, the components are used inside the root component of the application.<\/div>\n
        <\/div>\n
        <\/div>\n
        Components are characterized with template and logic with data flowing from the logic to the template and events emitted from the template to the logic.<\/div>\n
        <\/div>\n
        <\/div>\n
        Let\u2019s have a look at the root component of our application so that we can have an idea of how the application is mounted and how the component actually looks like.<\/div>\n
        <\/div>\n
        <\/div>\n
        \u00a0 \u00a0\"\"<\/div>\n
        <\/div>\n
        The component in the image above is known as the Single File component. A single file component consists of 3 sections first is the \u201cTemplate\u201d section which contains the HTML that will be rendered when our component gets mounted. Second, is the \u201cscript\u201d section that JavaScript codes such as the variables and the events, and the third section \u201cstyle\u201d has the styles for the component. So we can have our components’ HTML, CSS, and JavaScript code live in a single file with a .vue file extension.<\/div>\n
        <\/div>\n
        \u00a0 \u00a0\"\"<\/div>\n
        <\/div>\n
        The component passed into the\u00a0createApp\u00a0<\/em>function is used as the root component of our application and it is used for rendering while mounting the application. If we want to separate our CSS and Javascript code Vue also supports it.<\/div>\n
        <\/div>\n

        What are local and global components?<\/h2>\n
        <\/div>\n
        \n
        A local component is a component that is available where it is created or where it is imported in another context. The single-file component that we have seen above is an example of the local component.<\/div>\n
        <\/div>\n
        <\/div>\n
        Vue also provides us functionality to create global components that can be used anywhere in our application without the requirement to import\/export the component.<\/div>\n
        <\/div>\n
        Example of creating a global component referred from the official site,<\/div>\n
        \n
        \n
        <\/div>\n
          \n
        1. \/\/\u00a0javascript\u00a0code\u00a0\u00a0<\/span><\/li>\n
        2. <\/li>\n
        3. const<\/span>\u00a0app\u00a0=\u00a0Vue.createApp({})<\/li>\n
        4. app.component(‘component-a’<\/span>,\u00a0{<\/li>\n
        5. \u00a0\u00a0\/*\u00a0…\u00a0*\/<\/span><\/li>\n
        6. })<\/li>\n
        7. app.component(‘component-b’<\/span>,\u00a0{<\/li>\n
        8. \u00a0\u00a0\/*\u00a0…\u00a0*\/<\/span><\/li>\n
        9. })<\/li>\n
        10. app.component(‘component-c’<\/span>,\u00a0{<\/li>\n
        11. \u00a0\u00a0\/*\u00a0…\u00a0*\/<\/span><\/li>\n
        12. })<\/li>\n
        13. app.mount(‘#app’<\/span>)<\/li>\n
        14. \/\/\u00a0HTML\u00a0code\u00a0\u00a0<\/span><\/li>\n
        15. <div\u00a0id=“app”<\/span>><\/li>\n
        16. \u00a0\u00a0<component-a><\/component-a><\/li>\n
        17. \u00a0\u00a0<component-b><\/component-b><\/li>\n
        18. \u00a0\u00a0<component-c><\/component-c><\/li>\n
        19. <\/div><\/li>\n<\/ol>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
          \n
          One of the main disadvantages of globally registering components, if you’re using a build system like Webpack, globally registering all components, means that even if you stop using a component, it could still be included in your final build. This unnecessarily increases the amount of JavaScript your users have to download.<\/div>\n
          <\/div>\n
          <\/div>\n
          The solution for not including unnecessary javascript for your users is to define the components as plain javascript objects. This would help us as locally registered components are not also available in subcomponents.<\/div>\n<\/div>\n

          Use case of vue.js<\/h3>\n

          Vue. js is a progressive framework for JavaScript used\u00a0to build web interfaces and one-page applications<\/b>. Not just for web interfaces, Vue. js is also used both for desktop and mobile app development with Electron framework.<\/p>\n

          5 practical use cases of Vue.<\/b>\u00a0js<\/b><\/div>\n
          \n
            \n
          1. Navigation menu. Let’s build a simple navigation bar. …<\/li>\n
          2. Built-in editor. In the previous example, our model had only a couple of predefined values. …<\/li>\n
          3. Order form. This example shows the list of services and the total cost of the selected ones. …<\/li>\n
          4. Instant search. …<\/li>\n
          5. Switchable grid.<\/li>\n<\/ol>\n<\/div>\n

            \"\"<\/p>\n

            feature and advantage of using vue js<\/h3>\n
            Advantages of Vue.<\/b>\u00a0js<\/b><\/div>\n
            \n