I had a very interesting discussion recently. It was about describing the structure of some real-time application that has to support multiple users working with it at the same time. I don’t remember the exact task, but the core is:

Describe the structure of kanban board application with the following…

Suppose we have an object and we want to do something when it’s properties change. Probably we’ll start with something like that:

export default {
  data: () {
    return {
      obj: {
        prop: 1…

I’m writing it because it seems to be rather popular task that has not any well known common solution. Usually it all starts with some surprisingly strange `simple` solution that by the end transforms to the system I’m going to write about.

The task is to create and support weekly…

Assume you want to write some backend using node/express. That’s the good idea, it’s easy — you just write

const express = require('express')
const app = express()app.get('/', (req, res) => res.send('Hello'))app.listen(3000)

and that’s all you need to start. Then you realize that any backend is usually a queue…

I would like to name this tutorial like «Simple Nuxt Authentication» or something else with the word simple in the title, but this topic is not simple. At least, it does not go just out of the box.

For the beginner I would suggest to use the library like https://github.com/nuxt-community/auth-module…