by Matt Rothenberg

A Vue.js introduction for people who know just enough jQuery to get by

The logo for Vue.js

I’ve had a love-hate relationship with JavaScript for years.

I got to know the language by way of the design and development community’s favorite whipping boy, jQuery. You see, at the time I began learning JavaScript, as a “Designer who codes,” working with jQuery was a magical experience. I could make modals fadeIn and fadeOut . With a third-party library, I could add parallax scrolling to my portfolio with just a single function call. Nearly everything I could have possibly dreamed of was encapsulated in a single, ~100kb file…

And then Angular came out. I had no choice but to redo my entire portfolio with the framework. And then React came out. I had no choice but to redo my entire portfolio with the library. And then Vue.js came out. I had no choice but to redo my entire portfolio with the library… You see where this is going.

All jokes aside, I have greatly enjoyed honing my JavaScript chops through building things here and there with these different frameworks and libraries. I have read countless articles and tutorials in the process, but none has stuck with me more than Shu Uesugi’s piece, “React.js Introduction For People Who Know Just Enough jQuery To Get By.”

Shu takes readers — who are presumed to have some level of proficiency with JavaScript fundamentals and jQuery — on a journey through the world of React as they build a clone of Twitter’s “compose tweet” component.

This conceptual frame was quite helpful to me as someone who learns best by doing. Indeed, any time a new JavaScript library comes out, I find myself going back to the example from this article to test the waters. And so, I would like to borrow this frame as I step you all through my recent experience of learning Vue.

Before you begin the steps below, I highly encourage you to read Shu’s article. He does a fantastic job of walking you through the jQuery code you might write in order to implement some of these features. Thus, and so as to mitigate the risk of redundancy, I will focus on showing you the ins-and-outs of Vue.

What We’re Building

Most of us tweet (some more prolifically than others). So we are probably familiar with the User Interface component in the screenshot below.

Twitter’s “Compose Tweet” box

Believe it or not, this UI component is a great example of how Vue (and React, as per Shu) might improve your life as a JavaScript/jQuery developer. The elements of this component that we will focus on building today are:

The <textar ea> where users can enter their tweet

ea> where users can enter their tweet The <butt on> that is enabled/disabled as a function of how long the tweet is

on> that is enabled/disabled as a function of how long the tweet is A counter that indicates how many characters (out of 140) remain, and changes color to warn the user of this limit

A camera icon that, when clicked, allows users to attach photos to their tweet

A list of photos that have been attached

A button (per each photo) to remove it from the tweet

If You’re Stuck

If at any point you come across something that is confusing or poorly explained, don’t hesitate to tweet me at @mattrothenberg. Keep in mind as you read this article: it’s not you, it’s definitely me.

Let’s get started.

How We’re Building It

Today, we will be using CodePen to build our “Compose Tweet” component. For the uninitiated, CodePen is an online HTML/CSS/JavaScript editor akin to JSBin or JSFiddle. For each step, I’ll embed a CodePen with the relevant code.

Step 1: Scaffold The Project

The first thing we need to do, before writing any JavaScript, is to write the markup for our “Compose Tweet” component. Today we will be using Tachyons for almost all of our stylistic needs (so that we don’t have to write extraneous CSS, and can focus on the markup and JavaScript).

I am running with the assumption that you are pretty CSS savvy, so I will not spend time walking you through the Tachyons approach to styling (tl;dr so style, much classes, very functional).

In this CodePen I have also gone ahead and pulled in Vue via CDN. Indeed, one of the main selling points of Vue is the simplicity by which it can be integrated into a new or existing codebase.

With everything in place, let us get started on some feature work.

Step 2: Implement the First Feature — Tweet Button Should Initially Be Disabled

Feature Description: Disable the blue Tweet button until a user has entered at least one character in the textarea .

First things first, let us set up our Vue instance. As mentioned above, Vue has won the hearts and minds of Developers by its simplicity of installation and ease of use. We can construct a Vue instance with the following code.

new Vue({ el: '#twitterVue', data: { tweet: '' }, computed: { tweetIsEmpty: function() { return this.tweet.length === 0; } }})

Let me explain what is going on here —

el refers to the DOM element to which we are attaching our Vue instance. This should feel similar to instantiating a jQuery plugin by passing in a given selector, be it a class name or ID.

refers to the DOM element to which we are attaching our Vue instance. This should feel similar to instantiating a jQuery plugin by passing in a given selector, be it a class name or ID. data is an object that describe’s our instance’s data model, or state. We can access the attributes specified within this model both in our HTML — via a special curly brace syntax {{tweet}} — and within the instance itself (hint, look at the body of the tweetIsEmpty function)

is an object that describe’s our instance’s data model, or state. We can access the attributes specified within this model both in our HTML — via a special curly brace syntax — and within the instance itself (hint, look at the body of the function) computed is an object that describes, as you might guess, computed properties based on our data model. Instead of adding logic to our HTML, it is recommended to encapsulate this kind of state (or any derived value, for that matter) via functions defined on the computed key of our Vue instance.

Turning our attention now to the HTML, you will see that our markup has changed ever so slightly from the first CodePen. Specifically, we have made three changes.

We added the id twitterVue to the outermost div so that we could construct our Vue instance.

<div id="twitterVue">...</div>

2. We added the v-model directive to our textarea , thereby creating a two-way binding between user input and our instance’s data model. Now, any time a user types in the textarea , the tweet attribute on our instance’s data model is automagically updated.

<textarea v-model="tweet"></textarea>

3. We added the :disabled attribute to our button . The colon preceding disabled denotes that we would like to evaluate the content inside the quotes as a JavaScript expression. If we were to omit the colon, the content would be treated as a string. You’ll also note that we’ve added a few lines of CSS to give the disabled button a distinct visual styling.

<button :disabled="tweetIsEmpty">Tweet</button>

...

button[disabled] { cursor: not-allowed; opacity: .5;}

4. We also added a computed property on our instance called tweetIsEmpty . Note that this property is actually a function that returns a boolean value based on the length of our data model’s tweet attribute. Vue makes it dead simple to access your data model both in the HTML (as shown above) and in the instance itself. Thanks to the magic of two-way data binding, this function is evaluated when the value of tweet is updated. When the function evaluates to true, our button is disabled, and vice-versa.

tweetIsEmpty: function() { return this.tweet.length === 0;}

Admittedly, this felt like smoke and mirrors when I first got started with Vue. What helped me was to literally see what was happening to our data model under the hood as I interacted with the component. Since we can easily access our data model in our HTML via the aforementioned curly brace syntax, we can build a quick, visual feedback loop. Score!

<p>The value of <strong>tweet </strong>is: {{tweet}} </p><p>The value of <;strong>tweetIsEmpty</strong>is: {{ tweetIsEmpty}}</p>

Please feel free to repeat this step if anything along the way was confusing (either due to my poor writing or coding abilities, or due to Vue itself). Send a tweet or leave a comment if you have any particular questions.

Step 3: Implement the Second Feature — Show The Number of Characters Remaining

Feature Description: As a user types, show the number of characters remaining (out of 140) in the tweet. If a user has entered more than 140 characters, disable the blue Tweet button.

So far we have learned about two-way data binding and computed properties, concepts that are at the very core of Vue. It is our lucky day, because we can leverage these concepts to build our next feature: showing the users how many characters (out of 140) remain, and disabling the button if this limit is eclipsed.

Once again, I will step you through both the JavaScript and HTML changes required to implement this feature.

In our JavaScript, we have done a few things.

As a housekeeping measure, we enumerated the max length of a tweet (140 characters) as a constant, MAX_TWEET_LENGTH .

const MAX_TWEET_LENGTH = 140;

2. We added another computed property, charactersRemaining , which dynamically returns the difference between 140 and the length of the user-entered tweet.

charactersRemaining: function() { return MAX_TWEET_LENGTH - this.tweet.length;}

3. We renamed the old tweetIsEmpty property to tweetIsOutOfRange and updated the function’s logic accordingly. Note how we are using the computed charactersRemaining property to derive this value. Hooray for code reuse!

tweetIsOutOfRange: function() { return this.charactersRemaining == MAX_TWEET_LENGTH || this.charactersRemaining < 0; }

On the HTML side of things, we only have to make a few changes, thanks to the power of Vue’s two-way data binding.

<div class="flex items-center"> <span class="mr3 black-70">{{ charactersRemaining }}</span> <button :disabled="tweetIsOutOfRange" class="button-reset bg-blue bn white f6 fw5 pv2 ph3 br2 dim">Tweet</button></div>

For the visual learners out there, watch the magic:

Step 4: Implement the Third Feature: Conditional Styling of “Characters Remaining” indicator

Feature Description: When composing a Tweet, the color of the “characters remaining” indicator should change to dark red when only twenty characters remain, and light red when ten or fewer remain.

Manipulating an element’s style or class can be cumbersome with jQuery, and Vue offers a much cleaner way of doing so. Vue’s approach feels more declarative, in that you describe how you want something’s style to change (based, for example, on a given state) and you let Vue do the heavy lifting.

In the context of this feature, our “characters remaining” indicator has two such states, and a corresponding CSS class for each.

When between ten and twenty characters remain, the indicator should have the dark-red class When fewer than ten characters remain, the indicator should have the light-red class

By now your Vue brain should be shouting “COMPUTED PROPERTIES!” So, let us oblige this brain and wire up those properties.

underTwentyMark: function() { return this.charactersRemaining <= 20 && this.charactersRemaining > 10; },underTenMark: function() { return this.charactersRemaining <= 10;}

With our logic in place, let us take a look at one of the ways in which Vue handles conditional styling: the v-bind:class directive. This directive expects an object whose keys are CSS classes, and whose values are the corresponding computed properties.

{ 'dark-red': underTwentyMark, 'light-red': underTenMark }

By adding the directive to the span tag that encloses our “characters remaining” indicator, we have completed our feature.

<span v-bind:class="{ 'dark-red': underTwentyMark, 'light-red': underTenMark }"> {{ charactersRemaining }}</span>

Under the hood, and thanks to two-way data binding, Vue will handle the addition and removal of these classes as a function of the specified computed properties.

Step 5: Implement the Fourth Feature: “Attach Photo” UX

Feature Description: Allow users to attach a single photo to their tweet via a file picker dialog. When the photo has been uploaded, show it beneath the textarea , and allow users to delete the attachment by clicking the image

Fair warning: there is a lot going on in this section. The beauty is, despite this feature adding considerable functionality, we will not have to write that much code. So, let us start by breaking down the interaction design into steps.

User clicks the “Add Photo” button User sees a file picker dialog and can select one photo to upload Upon selecting the photo, a box appears underneath the textarea with the selected photo inside User clicks the circular X button to remove the photo User sees initial state from step 1

Up to this point, we have not yet done any event handling (listening to button clicks, input changes, etc). As you might expect, Vue makes it easy to handle such events by affording us the v-on directive (@ for short). By passing a method as a value of this directive, we can effectively listen to DOM events and run JavaScript when they are triggered.

Before diving into our feature work, some rapid-fire practice.

Event handling is as easy as adding the @click directive to a given button and adding a corresponding method to the methods key on our Vue instance.

<button @click="logNameToConsole">Log User's Name<;/button>...methods: { logNameToConsole: function() { if( this.name !== 'Donald Trump' ) { console.log(this.name); } else { console.warn('Sorry, I do not understand'); } },}

Back to our feature work… In this step, our markup and JavaScript have changed in the following ways:

We added a button with an @click directive. When a user clicks this button, the triggerFileUpload method will get called.

<button @click="triggerFileUpload">...</button>

So, in our JavaScript, let us add a methods key to our Vue instance with said method inside, as well as a data attribute for our photo.

data: { photo: null},computed: {},methods: { triggerFileUpload: function() { this.$refs.photoUpload.click(); // LOLWUT? },}

2. It is notoriously difficult to style HTML5 file inputs. One workaround involves putting an input in the DOM and hiding it with CSS. In order for the browser to open the native file picker, this input must be clicked. How it gets clicked, and how the client handles what the user uploads, though, is a different matter.

In our markup, we’ve added one such input and hidden it with a special hide class. We have also added a few other attributes worth calling out:

<input ref="photoUpload" @change="handlePhotoUpload" type="file" class="hide">

The ref attribute is used to register a reference to a given DOM element. Given this reference, we can access the DOM element in our JavaScript code with this.$refs.photoUpload . Which means we can programmatically trigger a click() event on this element, thereby circumventing the challenge described above.

attribute is used to register a reference to a given DOM element. Given this reference, we can access the DOM element in our JavaScript code with . Which means we can programmatically trigger a event on this element, thereby circumventing the challenge described above. Clicking on the input is one thing; handling the file that the user uploads is another. Luckily, Vue allows us to attach a handler to the input’s change event via the @change directive. The method that we pass to this directive will be invoked after a user selects a file from the file picker. That method, handlePhotoUpload , is fairly straightforward

handlePhotoUpload: function(e) { var self = this; var reader = new FileReader(); reader.onload = function(e) { // Set that base 64 string to our data model's 'photo' key self.photo = (e.target.result); } // Read upload file as base 64 string reader.readAsDataURL(e.target.files[0]); }

Take a deep breath, because we are almost done with this feature!

Once a user has uploaded a photo, we need to show a box underneath the textarea with the selected photo inside. Just as the conditional styling of elements is a breeze with Vue, so too is the conditional rendering, or display of elements. You’ll note that in our HTML, we have added the following markup underneath the textarea .

<div v-if="photoHasBeenUploaded"> <figure> <button @click="removePhoto"> ... </button> <img v-bind:src="photo"> </figure></div>

Vue offers a handful of template helpers ( v-if , v-show, v-else , etc) to help you show and hide content conditionally. When the JavaScript expression passed to this directive evaluates to true, the element is rendered, and vice-versa.

In our case, we added a v-if statement that evaluates the computed property photoHasBeenUploaded .

photoHasBeenUploaded: function() { return this.photo !== null;}

When that function evaluates to true — when the photo key of our data model is not equal to null — the entire div gets rendered. Voilà!

And inside that div we render two elements:

The image that was attached, by passing the contents of our data model’s photo key to Vue’s v-bind:src directive A delete button that features another example of the @click handler, this particular one invoking a function that “removes” the photo by setting our data model’s photo key to null.

removePhoto: function() { this.photo = null;}

We are almost there.

Step 6: Correction, user can attach “photos”

So, we can effectively handle a user attaching one photo to the Tweet, but what if she would like to upload many photos?

By now, you should be thinking something to the effect of: “I guess the only significant change here is being able to show multiple images in that box that appears conditionally beneath the textarea, considering we have already wired up our event handlers…” And you are correct! Let us take a look at the steps we need to follow

We need to update our data model by changing photo to photos , the new key being an array of base64 strings (not a single base64 string)

data: { photos: []},

2. We need to update our computed property photoHasBeenUploaded to check against the length of our new photos key, which is now an array.

photoHasBeenUploaded: function() { return this.photos.length > 0;}

3. We need to update our input @change handler to loop over the uploaded files and push them onto our photos key.

handlePhotoUpload: function(e) { var self = this; var files = e.target.files;

for(let i = 0; i < files.length; i++) { let reader = new FileReader();

reader.onloadend = function(evt) { self.photos.push(evt.target.result); }

reader.readAsDataURL(files[i]); }},

On the HTML side, however, we must embark into new territory. Iterating over data and rendering content with jQuery can be cumbersome.

var array = [1, 2, 3, 4, 5];var newHTML = [];for (var i = 0; i < array.length; i++) { console.log('UGHHHHHH'); newHTML.push('<span>' + array[i] + '</span>');}$(".element").html(newHTML.join(""));

Thankfully, Vue offers an abstraction over this procedure by way of the v-for directive. This directive expects you to provide an expression in the form of (thing, index) in collectionOfThings , where collectionOfThings is the source array, thing is an alias for the array element being iterated on, and index is, well, the index of that element.

A prototypical example might look like this:

Where before we had a singular figure element for the user-uploaded photo, we will now have N figure tags corresponding to the length of the photos source array.

Lucky for us, our markup doesn’t have to change too drastically since the overall structure of the design is still the same.

<figure v-for="(photo, index) in photos"> <button @click="removePhoto(index)"> ... </button> <img v-bind:src="photo" class="h3 w3"></figure>

The one change that we need to make revolves around the removePhoto method which, before, set the singular photo key on our data model to null . Now, since we have N number of photos, we must pass the element’s index to the removePhoto method and pull that element out of the array.

removePhoto: function(index) { this.photos.splice(index, 1);}

Step 7: Animation + Extra Credit

In Twitter’s UI, the “Compose Tweet” component opens in a modal. For our grand finale, I would like to apply all of the Vue techniques we have learned so far and introduce one more: transitions.

Transition Lifecycle

A word of caution, transitions are a vast subject in Vue land. We are going to examine and implement a thin slice of this functionality, namely integrating a 3rd party animation library, Velocity JS, with Vue.

In a nutshell, Vue provides a transition component that allows you to add enter/leave animations for the element contained within, provided the element is set to be displayed conditionally via, for example, a v-if or v-show directive.

<transition name="modal-transition" v-on:enter="modalEnter" v-on:leave="modalLeave"> <div v-if="modalShowing"> <!-- Our modal contents goes here ! --> </div></transition>

In our example, we have attached two methods that correspond with two events in the transition lifecycle: v-on:enter and v-on:leave . We have thusly added these method definitions to our Vue instance, deferring to Velocity JS to fade our modal in and out.

methods: { modalEnter: function(el, done) { Velocity(el, 'fadeIn', { duration: 300, complete: done, display: 'flex' }) }, modalLeave: function(el, done) { Velocity(el, 'fadeOut', { duration: 300, complete: done }) }}

As mentioned above, the transition will fire when the element contained within is conditionally set to display. So, on the inner div of our transition component, we have added a v-if declaration whose value is a boolean modalShowing . Let us update our instance’s data model accordingly.

data: { modalShowing: false}

Now, when we want to show the modal, all we have to do is set that boolean to true!

<button @click="showModal">Compose Tweet</button>

And write a method to match.

hideModal: function() { this.modalShowing = false;},showModal: function() { this.modalShowing = true;},

With some CSS trickery, we have also attached a click event handler to the backdrop, so users can hide the modal. Score!

<div @click="hideModal" class="backdrop"></div>

Conclusion

Well, I hope that was not too painful (and that you learned a thing or two along the way). We only took a look at a small sliver of what Vue has to offer, though, as mentioned above, these concepts are crucial to unlocking the potential of Vue.

I admit, it is unfair to compare Vue to jQuery. They are products of different times, with quite different use cases. However, for those who have struggled their way to learn DOM manipulation and event handling through jQuery, I hope these concepts are a breath of fresh air that you can apply to your workflow.