Cover image for Yet Another Damn ToDo App in Vue.js

Yet Another Damn ToDo App in Vue.js

raymondcamden profile image Raymond Camden Originally published at raymondcamden.com on ・4 min read

So last week I published my thrilling post on building a ToDo app in Vue.js (“Another Damn ToDo App in Vue.js”). As promised, I’m following up on that post with an “enhanced” version of the application. The previous version was quite simple. It used Vue as a script tag, not a full Vue application, and stored the ToDos in memory. That meant on every reload the data was lost.

In this version I made three main changes:

  • First I switched over to a complete Vue application.
  • I added Vuex as a way to put my all my data access code in one place.
  • I used IndexedDB to persist the ToDos over every load. This is still only per device so if you open the app on another machine or in another browser, it won’t have the same data.

Let me explain each step of this.

Switching to an Application

This part should be relatively straight forward. The original version of my application (which you can see here) was built with just a script tag and some code, no build process. There’s nothing wrong with that! But with the idea that I’m enhancing this application to make it more powerful, it made sense for me to move this into an application.

I simply used the Vue CLI to scaffold a new application, using the -b option to keep it clean of stuff I didn’t need.

With the new application, I copied over the HTML, CSS, and JavaScript from the first version and ensured everything still worked. A tip I like to share from time to time is to take baby steps as you develop.

Adding Vuex

I then added Vuex to the application. The idea being that my application components will ask for their data from Vuex and Vuex will handle retrieving, updating, and so forth. This required changes in the front-end component, so let’s take a look. First, the HTML as the change here is super minor.

    <div id="app">

        <tr v-for="todo in sortedToDos" :key="todo.id">
            <td><span :class="{todoDone:todo.done}">{{todo.text}}</span></td>
                <button @click="toggleDone(todo)">
                    <span v-if="todo.done">
                    </span><span v-else>

            <input type="text" v-model="todoText">
            <button @click="saveToDo">Save ToDo</button>


So literally the only change here is in the index in my loop. Previously my todos didn’t have a primary key so I had to use the loop index as the key. Now my todos do have one so I use that instead. ANd that’s it. The JavaScript changed quite a bit more though.

import { mapGetters } from 'vuex';

export default {
    data() {
        return {
    created() {
    computed: {
    methods: {
        saveToDo() {
            if(this.todoText === '') return;
            this.$store.dispatch('saveToDo', { text:this.todoText, done:false} );
            this.todoText = '';         
        toggleDone(todo) {
            this.$store.dispatch('toggleToDo', todo);

First, I import mapGetters. This Vuex utility makes it easier to use getters from Vuex, which act like computed properties. My created method calls an action on the store that will fetch our data. Both saveToDo and toggleDone now call the store to handle their logic.

Implementing IndexedDB

For the most part, I copied the work I did back in October last year when I first discussed this topic, Using IndexedDB in Vue.js. My store handles the data, but the persistence is handled by another script, idb.js. (That isn’t the best name, but whatevs…) Here’s my store:

import Vue from 'vue'
import Vuex from 'vuex'

import idb from '@/api/idb';


export default new Vuex.Store({
  state: {
    todos: []
  getters: {
    sortedToDos(state) {
      return state.todos.slice().sort((a,b) => {
        if(!a.done && b.done) return -1;
        if(a.done && b.done) return 0;
        if(a.done && !b.done) return 1;
  mutations: {
    addToDo(state, todo) {
    clearToDos(state) {
      state.todos = [];
    toggleToDo(state, id) {
      state.todos = state.todos.map(t => {
        if(t.id === id) t.done = !t.done;
        return t;

  actions: {
    async loadToDos(context) {
      context.state.todos = [];
      let todos = await idb.getToDos();
      todos.forEach(t => {
        context.commit('addToDo', t);
    async saveToDo(context, todo) {
      await idb.saveToDo(todo);
    async toggleToDo(context, todo) {
      todo.done = !todo.done;
      await idb.saveToDo(todo);

Note that I’m importing that second, new script, and I don’t actually ever manipulate the state values. I load them from logic in the script. I manipulate a copy in my getter. But reading and writing is done in idb.js. That code is pretty much exactly the same as the blog post mentioned above, but here it is:

const DB_NAME = 'tododb';
const DB_VERSION = 1;
let DB;

export default {

    async getDb() {
        return new Promise((resolve, reject) => {

            if(DB) { return resolve(DB); }
            console.log('OPENING DB', DB);
            let request = window.indexedDB.open(DB_NAME, DB_VERSION);

            request.onerror = e => {
                console.log('Error opening db', e);

            request.onsuccess = e => {
                DB = e.target.result;

            request.onupgradeneeded = e => {
                let db = e.target.result;
                db.createObjectStore('todos', { autoIncrement: true, keyPath:'id' });
    async getToDos() {

        let db = await this.getDb();

        return new Promise(resolve => {

            let trans = db.transaction(['todos'],'readonly');
            trans.oncomplete = () => {

            let store = trans.objectStore('todos');
            let todos = [];

            store.openCursor().onsuccess = e => {
                let cursor = e.target.result;
                if (cursor) {

    async saveToDo(todo) {

        let db = await this.getDb();

        return new Promise(resolve => {

            let trans = db.transaction(['todos'],'readwrite');
            trans.oncomplete = () => {

            let store = trans.objectStore('todos');



Again, if you want more details on how this works, check out my earlier post (and feel free to ask me in a comment below).

And that’s pretty much it. You can see the complete source code of the application here: https://github.com/cfjedimaster/vue-demos/tree/master/todos2. I also have a live version you can run here: https://todos2.raymondcamden.now.sh/

Header photo by Glenn Carstens-Peters on Unsplash


Editor guide