Extending VueJS Components

Extending VueJS Components

Do you have components in your Vue app that share similar options, or even template markup?

It’d be a good idea to create a base component with the common options and markup, and then extend the base component to create sub components. Such an architecture would help you apply the DRY principle in your code (Don’t Repeat Youself) which can make your code more readable and reduce the possibility of bugs.

Vue provides some functionality to help with component inheritance, but you’ll also have to add some of your own ingenuity.

Example: survey questions

Here is a simple survey made with Vue.js:

You’ll notice that each question has a different associated input type:

  1. Text input
  2. Select input
  3. Radio input

read more

Single Page App Backends: Where Laravel Beats Node.js

Single Page App Backends: Where Laravel Beats Node.js

I’ve been commissioned to write a book about building full stack Vue.js apps. Since many Laravel developers are interested in Vue (Vue now ships with Laravel), the publisher wants the book to focus on full stack Vue.js with Laravel.

In preparing for the book I knew I would have to answer a very important question for myself: why would anyone even want to use Laravel as backend for a single page app when they can use Node.js?

Node.js advantages

Like many web devs who learned to code in the last decade, I started out with PHP. But as I got interested in frontend development and SPAs (single page apps), I eventually made the switch to full stack JavaScript and I hadn’t really looked back since.

Node.js has some very clear advantages as an SPA backend:

  1. One language in the project (JavaScript) means it’s simply easier to code.
  2. There’s opportunity to share code between the frontend and backend apps or even make the app isomorphic.
  3. Node.js allows server-side rendering. This means you can render your page on the server before it hits the browser, allowing users to see the page quicker. (There are attempts to achieve this with PHP/JS extensions, but for the time being, these do not work with many SPA frameworks like Vue, and if they do, they’re much slower).
  4. Node has non-blocking I/O and is better at handling concurrent requests (PHP can do this now too, but again, slower).

Stuck with PHP

Given all of the above, my assumption for why you’d use PHP for a SPA backend is because you must be stuck with it, and Laravel is chosen because it’s simply the best of a bad situation.

You might be stuck with PHP if:

read more

Switching From React To Vue.js

Switching From React To Vue.js

So you’re a React developer and you’ve decided to try out Vue.js. Welcome to the party!

React and Vue are kind of like Coke and Pepsi, so much of what you can do in React you can also do in Vue. There are some important conceptual differences though, some of which reflect Angular’s influence on Vue.

I’ll focus on the differences in this article so you’re ready to jump into Vue and be productive straight away.

How much difference is there between React and Vue?

React and Vue have more similarities than differences:

  • Both are JavaScript libraries for creating UIs
  • Both are fast and lightweight
  • Both have a component-based architecture
  • Both use a virtual DOM
  • Both can be dropped into a single HTML file or be a module in a more sophisticated Webpack setup
  • Both have separate, but commonly used, router and state management libraries

The big differences are that Vue typically uses an HTML template file where as React is fully JavaScript. Vue also has mutable state and an automatic system for re-rendering called “reactivity”.

We’ll break it all down below.

Components

With Vue.js, components are declared with an API method .component which takes arguments for an id and a definition object. You’ll probably notice familiar aspects of Vue’s components, and not-so-familiar aspects:

read more

How To (Safely) Use A jQuery Plugin With Vue.js

How To (Safely) Use A jQuery Plugin With Vue.js

It’s not a great idea to use jQuery and Vue.js in the same UI. Don’t do it if you can avoid it.

But you’re probably reading this not because you want to use jQuery and Vue together, but because you have to. Perhaps a client is insisting on using a particular jQuery plugin that you won’t have time to rewrite for Vue.

If you’re careful about how you do it, you can use jQuery and Vue together safely. In this article I’m going to demonstrate how to add the jQuery UI Datepicker plugin to a Vue project.

And just to show off a bit, I’m even going to send data between this jQuery plugin and Vue!

See it working in this JS Bin.

jQuery UI Datepicker

jQuery UI Datepicker

The problem with using jQuery and Vue together

Why is doing this potentially hazardous?

Vue is a jealous library in the sense that you must let it completely own the patch of DOM that you give it (defined by what you pass to el). If jQuery makes a change to an element that Vue is managing, say, adds a class to something, Vue won’t be aware of the change and is going to go right ahead and overwrite it in the next update cycle.

Solution: use a component as a wrapper

Knowing that Vue and jQuery are never going to share part of the DOM, we have to tell Vue to cordon off an area and give it over to jQuery.

read more

WTF is Vuex? A Beginner's Guide To Vue's Application Data Store

WTF is Vuex? A Beginner's Guide To Vue's Application Data Store

This article was originally posted here on Medium on 2016/11/30


Vuex. Is it pronounced “vewks”, or “veweks”? Or maybe it’s meant to be “vew”, pronounced with a French-style silent “x”?

My trouble with understanding Vuex only began with the name.

Being an eager Vue developer I’d heard enough about Vuex to suspect that it must be an important part of the Vue ecosystem, even if I didn’t know what it actually was.

I eventually had enough of wondering, so I went to the documentation with plans of a brief skim through; just enough to get the idea.

To my chagrin I was greeted with unfamiliar terms like “state management pattern”, “global singleton” and “source of truth”. These terms may make sense to anyone already familiar with the concept, but for me they didn’t gel at all.

The one thing I did get, though, was that Vuex had something to do with Flux and Redux. I didn’t know what those were either, but I figured it may help if I investigated them first.

After a bit of research and persistence the concepts behind the jargon finally started to materialise in my mind. I was getting it. I went back to the Vuex documentation and it finally hit me…Vuex is freaking awesome!

I’m still not quite sure how to pronounce it, but Vuex has become an essential piece in my Vue.js toolbelt. I think it’s totally worth your time to check it out too, so I’ve written this primer on Vuex to give you the background that I wish I’d had.

Understanding The Problem That Vuex Solves

To understand Vuex it’s much easier if you first understand the problem that it’s designed to solve.

read more