What's the difference between v-if and v-show in Vue.js?

V-if vs. V-Show

What is the difference between v-if and v-show and when should you use which?

Well, quite simply, v-if determines whether or not to render the element AT ALL, while v-show simply hides it from view setting "display" to "none."

When you use v-if, the rendering of that element is destroyed, which means the listeners and components nested within are also destroyed. This saves memory and improves your apps performance. They can always be recreated later, too.

V-if is also considered lazy. That means it only loads at the moment the conditional in the if block is finally determined to be true.

However, sometimes you don't want to destroy your components or elements and want to keep the listeners and child components active. In that case, you'd probably want to stick with "v-show."

Unlike "v-if," "v-show" elements are rendered at the same time as everything else.

So when should you use v-if or v-show.


Use "v-show" if:

  • You plan on toggle that element often, since it has lower toggling costs
  • You need to listen to changes on element while it is hidden
  • If you want it to render along side the rest of your app


Use "v-if" if:
  • If you don't plan on toggling the element often
  • If you don't plan on listening to the hidden element and don't need access to its children in the DOM
  • You want to lazy-load the component/element

Comments

Post a Comment

Popular posts from this blog

Vue Broadcasting (Part 1)

Broadcast across all Vue instances Vue comes with the very handy feature of broadcasting events through the   $on   and  $emit  instance methods. Generally this is used to communicate between parent and child components. However, often times developers will attach an instance to the global  window  object to be able to communicate across all Vue instances. This is a great convenience but let's create a more scoped and portable solution by simply creating an exported VueEvent class: class VueEvent {     /**      * Event broadcaster class constructor.      *      * @constructor      */     constructor () {         this.vue = new Vue();     }     /**      * This will emit a broadcast that can be utlized by an active Event listener.      *      *...
Read more

Vue.js: Automatically Import Components

Automatically import all single file components during Webpack 2 bootstrap   Many developers using Webpack and utilizing Vue's Singe File Components load each component manually, one-by-one within an app or bootstrap file. However, Webpack comes with configuration options that can automate this process by instantiating the Vue component to match the file name. Let's take a look at our simple Webpack config function that can be used to automatically require our components. // Require and instantiate our components function requireAllComponents(requireContext) {     let keys = requireContext.keys();     return requireContext.keys().map(key => {         let pathMap = key.split('/'),             label = pathMap[pathMap.length - 1].slice(0, -4).replace(/([A-Z])/g, '-$1').slice(1).toLowerCase();         Vue.component(label, requireContext(key));     }); } N...
Read more

Vue.js vs Angular 1.0 (Part 2)

Which is better Vue.js or Angular 1.0 (Part 1)? Let's take a basic look at Vue.js vs. Angular: Components and Directives One of the biggest complaints from users of Angular 1.0 was the muddy nature of service providers and when to use which for what. Services, Factories, Providers, Directives, Components - there never seemed to be a clear, concise answer on how they should be used. With Vue, you have components and directives. With Vue there are components and directives, and the dilineation is very clear. WINNER:  Vue.js Community Support While Angular used to be the hottest framework around, it slowly started fizzling out as talks of Angular 2.0 came around, and React entered the scene. Many of the popular libraries are no longer updated and Vue seems to be taking its place. WINNER:  Vue.js Speed and Performance In benchmark tests, Vue outperforms Angular 1.0. With all the dirty checking and constant watchers, your Angular application will...
Read more