What's New in Nuxt.js 2.8.0

What's New in Nuxt.js 2.8.0

All the good-to-know new features in version 2.8.0 of Nuxt JS, with examples

Nuxt.js

Nuxt is a framework built for creating Vue applications. These Vue applications can be a single page application, a static generated application or a universal application. Nuxt presets all the configuration needed to make developing a Vue Application more enjoyable.

**Nuxt **is made for Vue applications, it is an even easier way to build Vue apps, as Vue is pretty easy to use already
Nuxt helps you build Server Side Rendered applications very seamlessly. This is because most of the complicated configurations associated with middleware, routing, state management and asynchronous data are baked into it. Nuxt is to Vue what Next is to React.

Getting started: create-nuxt-app

To get started quickly, the Nuxt.js team has created a scaffolding tool create-nuxt-app. This is just like the create-react-app for React projects. Make sure you have npx installed (npx is shipped by default since NPM 5.2.0)

$ npx create-nuxt-app <project-name>

Or with yarn:

$ yarn create nuxt-app <project-name>

It will ask you some questions:

  1. Choose between integrated server-side frameworks: None (Nuxt default server), Express, Koa, Hapi, Feathers, Micro, Adonis.
  2. Choose your favorite UI framework: None (feel free to add one later), Bootstrap, Vuetify, Bulma, Tailwind, Element UI, Ant Design Vue, Buefy.
  3. Choose your favorite testing framework: None (feel free to add one later), Jest, AVA.
  4. The Nuxt mode you want (<a href="https://nuxtjs.org/guide#single-page-applications-spa-" target="_blank">Universal</a> or <a href="https://nuxtjs.org/guide#single-page-applications-spa-" target="_blank">SPA</a>)
  5. Add axios module to make HTTP request easily into your application.
  6. Add EsLint to Lint your code on save.
  7. Add Prettier to prettify your code on save.

When answered, it will install all the dependencies so the next step is to navigate to the project folder and launch it with:

$ cd <project-name>
$ npm run dev

The application is now running on http://localhost:3000.

Few days ago the newest version of Nuxt JS was released, version 2.8.0 and these are the features that shipped with it:

Better Developer Experience

In this new version 2.8.0, the Nuxt team worked on a few new features to make the developer experience even better than it already is. These features will be discussed below.

Consola and adding SSR logs

Consola is a pretty looking easy to use and elegant console logger for Node JS and your web browser. It has a fancy output with fallback for minimal environments, it also contains pluggable reporters with a seamless and consistent command line interface. It supports tags, web browsers and mocking. You can install it with any of the popular package managers

Using yarn:

yarn add consola

Using npm:

npm i consola

Consola in action looks like the gif below, you can see how fancy the logged messages now appear.

Also in addition to Consola, the Nuxt team also added another feature for the console to help declutter the browser console. They kept in mind that developers regularly log messages to test out functions or features and also caught exceptions are also displayed in the console by default. In a bid to make the browser console look a bit more organised and clearer, SSR logs were added to be a kind of expandable and collapsible feature, like UI drop-downs.

Build indicator update

This is a feature I love so much, Nuxt JS is way too fast that most times you do not even get to know if your code rebuilt while on your browser, especially if it is a little change in a particular file. The Nuxt team has come up with this simple feature that shows a Nuxt logo sign in your browser indicating component rebuild just took place. It looks like this:

You see the percentage roll almost in a second to a 100, pretty cool for projects with distributed teams or people working on the same project from different machines.

File change updates

Before this new version of Nuxt, the team observed that the patterns used for listening to file changes contained some duplicates. These duplicates were all removed. Also, there has been an initially used workaround for recreating the watcher on raw events on linux, since the chokidar fix it is no longer needed anymore so it was also removed. All major patterns were also looked into to make them less greedy by always only listening for supported file extensions. A good example is listening on a directory without the supported file extensions could be prone to unnecessary reloads due to file changes which are not used by Nuxt. Eg *.swp, *~ or *.bak files used by editors.

Port and new watch settings

In this new version 2.8.0, the Nuxt team has set up watches for pages/ creation when default page displayed, this is the same change that was implemented for store/ but now applied for pages/ creation. Also starting from this new version, Nuxt will re-use the same port when randomly assigned when restarting in development environment.

Renderer updates

In version 2.6.3 an issue was reported with reproduction links showing that there was a problem with the renderer ignoring injection commands. Nuxt apps should not load scripts if the inject property for the bundler renderer in the config file is false. It was seen to still load some scripts. In response, in this version the render.injectScripts option has been added to Nuxt and support for render.ssrLog used to control SSR logs was also added.

List of Bugs fixed

In the following places, bugs were identified and fixed in this new Nuxt JS version:

  • Vue-renderer: Safe format for SSR logs were added and User-Agent‍ to Vary header in modern server mode was also added.
  • Server: Now returns listen when listen is called and preserve random port when restarting your server.
  • Builder: Watch for pages/ creation when default page displayed was setup and it now only listens for file changes for supported extensions.
  • Generator: Single page application fallbacks are now minified.
  • Types: Type definition was added for functional babel.presets
  • Vue-app: Trailing slash in vue-router non-strict mode is now removed, catch handlers are no more attached to already loaded components. Also fixPrepatch in-out transition was fixed.
  • Utils: serializeFunction for edge cases was handled.
Dependency upgrades

In this new version, the following dependencies were upgraded so take note as you update:

Conclusion

This has been a quick overview of all the new features and bug fixes of the new Nuxt JS version. It also contains a getting started guide for beginners. Happy hacking!

How to build enterprise Vue.js applications with Nuxt?

How to build enterprise Vue.js applications with Nuxt?

Learn How to build enterprise Vue.js applications with Nuxt: Nuxt is a progressive framework based on Vue.js to create modern web applications. It is based on Vue.js official libraries (vue, vue-router and vuex) and powerful development tools (webpack, Babel and PostCSS). Nuxt goal is to make web development powerful and performant with a great developer experience in mind.

Nuxt is a progressive framework based on Vue.js to create modern web applications. It is based on Vue.js official libraries (vue, vue-router and vuex) and powerful development tools (webpack, Babel and PostCSS). Nuxt goal is to make web development powerful and performant with a great developer experience in mind.

  1. Based on Vue-router and Vuex, it also uses Webpack, Babel and PostCSS.

  2. Goal, make web development powerful and performant.

Ok, so a sales pitch, what else?

The WHAT and WHY

Ok, so we love using Vue.js, it works great to use a router, a store, adding UI and so on, so why should we consider Nuxt?

The answer is SSR, Server side rendering

Why is that such a big deal? Well, search engines, they were made to crawl static pages and most SPA frameworks don't produce static pages but dynamic pages. This causes a problem if you want your app's SEO, to be any good, i.e end up high up on a Google search result. If you have a productivity app you might not care about that so much but if you have an e-commerce store you might be out of business if you haven't got this aspect covered.

Is that all Nuxt offer?

There is more. Nuxt makes it easy to bring in things such as code-splitting. Code splitting is an important aspect of the user experience. It allows us to only load as much of our app initially that's needed. It works like this, imagine the user visits your site. You only load a tiny portion of the app so the user perceives you got a fast-loading app - everyone's happy. As the user discovers more and more of your app they start navigating to other parts of it.

At this point, we load in the code needed for that new part the user is navigating to. This approach does a lot for the user experience, especially in places where the network connection is not that good. Having this for free in Nuxt is a big deal.

There is more to Nuxt of course, like hot module replacement, being able to load async data before SSR, a great approach to working with Sass, Less and so on.

Features

Here's a full list of all features Nuxt is offering:

  • Write Vue Files (*.vue)
  • Automatic Code Splitting
  • Server-Side Rendering
  • Powerful Routing System with Asynchronous Data
  • Static File Serving
  • ES2015+ Transpilation
  • Bundling and minifying of your JS & CSS
  • Managing <head> element (<title>, <meta>, etc.)
  • Hot module replacement in Development
  • Pre-processor: Sass, Less, Stylus, etc.
  • HTTP/2 push headers ready
  • Extending with Modular architecture

That's quite the list right?

SSR and code splitting is what really sells it for me though. How about we try to learn it next?

Schema, lifecycle

Let's try to get ourselves a mile-high view of Nuxt. There are some steps from the incoming request to a rendered page.

In Nuxt we use a directive called <nuxt-link> to navigate between pages.

  1. nuxtServerInit, a store is part of your next app. This is an action we can define in the store if we want. It can be used to place data in the store the first thing we do, like a logged-in user. Read more here
  2. middleware, middleware are custom functions that can run before the rendering of a route. You could, for example, ensure that the user is properly authenticated before being able to see a specific route. Read more here
  3. validate, in this step, we validate that we are dealing with a valid request, for example, we could be validating that an incoming request has the correct route parameters
  4. asyncData() & fetch(), here we have the chance of fetching data asynchronously that will be part of the SSR rendering, for example, we could be fetching translations or some other data we need to render our page
  5. Render, here we render the page

SPA or SSR mode

If for any reason, you prefer not to use server-side rendering or need static hosting for your applications, you can simply use SPA mode using nuxt --spa.

In combination with the generate feature, it gives you a powerful SPA deployment mechanism without the need to use a Node.js runtime or any special server handling.

read more about available commands here:

https://nuxtjs.org/guide/commands

SSR, Static site generation

The big innovation of Nuxt.js comes with the nuxt generate command.

When building your application, it will generate the HTML for every one of your routes and store it in a file.

How does that work?

-| pages/
----| about.vue
----| index.vue

turns into

-| dist/
----| about/
------| index.html
----| index.html

Great for crawlers :)

Hosting

Of course, you need to host your app somewhere. Currently, Netlify offers a great and easy way to do so with a simple command:

https://vueschool.io/lessons/how-to-deploy-nuxtjs-to-netlify?friend=nuxt

Creating an App

There are two ways to create apps in Nuxt:

  1. Wizard, Using create-nuxt-app, this will trigger a wizard where you are asked to add/opt in to different things
  2. Manually, A simple NPM install of nuxt and you need to define most things yourself.

Create an app with create-nuxt-app

We can use the command create-nuxt-app to get a full-fledged project. The only thing we need to do is choose among different options.

Let's run the following command:

npx create-nuxt-app <project-name>

or yarn:

yarn create nuxt-app <project-name>

This triggers a dialog, first choose Server-side framework:

-1- server-side framework

This is what will help us to do things like server side rendering that we use for static site generation.

  • None (Nuxt default server)
  • Express
  • Koa
  • Hapi
  • Feathers
  • Micro
  • Fastify
  • Adonis (WIP)

-2- select UI library

Of course you want your app to look good. Below are all the most known UI libraries that will be included in your project.

Then select UI library:

  • None (feel free to add one later)
  • Bootstrap
  • Vuetify
  • Bulma
  • Tailwind
  • Element UI
  • Ant Design Vue
  • Buefy
  • iView
  • Tachyons

-3- choose Testing framework

Do you want testing? No? Well, you need it. Jest and AVA are both good options.

  • None (feel free to add one later)
  • Jest
  • AVA

-4- select mode

This is where we select to have our app server side rendered or not. I'd go with Universal myself.

Select Universal or SPA mode

-5- http

fetch works of course but it's kind of nice when you can use a battle tested library like axios.

Add axios module for HTTP requests

-6- linting

You do lint right? We want our code to look consistent.

Add ESLint

-7- prettier

Add Prettier

-8- launch app

Launch app

cd <project-name>
npm run dev

the app should now be running on http://localhost:3000.

That was simple right? You opted into some tried and testing libraries that are sure to make your app better.

Below is your project overview, the result of running the creation tool.

Get started, from scratch

Let's have a look at the second approach, creating our app from scratch. First, we create a directory for our app to live in:

mkdir <project-name>
cd <project-name>

Update package.json

Next, let's add the necessary command to package.json so we can start up our app from the terminal:

{
  "name": "my-app",
  "scripts": {
    "dev": "nuxt"
  }
}

Now we can type npm run dev, to start the app.

Install nuxt

Next, let's install the nuxt library itself and save a reference to it in package.json:

npm install --save nuxt

Pages directory

Nuxt has some great conventions, so creating directories with certain names has meaning. That is the case with the directory pages. Everything, with file ending .vue, that is placed under the pages directory, will turn into a route.

<!-- index.vue -->
<template>
  <h1>Hello world!</h1>
</template>

Now run

npm run dev

This will start up our app. Let's go to the browser at http://localhost:3000 and have a look.

We have an app :)

Now try changing the template in index.vue, note how the change is reflected in the browser. This is because Nuxt comes with hot module reloading, it responds to changes.

Demo - SSR

Let's demonstrate the server-side rendering and how that works. As we mentioned before placing files under specific directories have meaning. We will continue to work with our pages directory.

This time, let's do the following:

  • Create a file products.vue under pages
  • Generate static site

Create a file

Let's create products.vue, under pages directory, with the following content:

<!-- products.vue -->
<template>
  <h1>Products</h1>
</template>

Our directory pages should now look like this:

-| pages/
---| index.vue
---| products.vue

Generate static site

Next up, let's generate those static files to make search engines everywhere happy.

We do this with the help of nuxt generate. Let's add that command to package.json and its scripts section like so:

"generate": "nuxt generate"

Next we run npm run generate, and we get a dist directory created, looking like so:

We can now easily host the content under dist using a tool, like for example http-server.

It looks like this in the browser:

As you can see http://localhost:5000/products/ and http://localhost:5000/products/index.html lead to the same place.

Working with Assets

Additionally to the pages directory, there's another directory that has special meaning. It's called assets. In there you can put images as well as stylesheets.

Working with image assets

Let's give it a try by doing the following

  • Creating assets directory and place a sample image file in there
  • Refer to sample image file in a Component

Create assets

We create our assets directory and place a file budapest.jpeg in there. Now your directory should look like the following:

-| assets/
---| budapest.jpeg
-| pages
--- | products.vue

Refer to asset

This time we want render our image asset. For this we will update products.vue to:

<!-- products.vue -->
<template>
  <div>
    <h1>Products</h1>
    <img src="~/assets/budapest.jpeg" alt="image" />
  </div>
</template>

What if we want to set this from code though? Then we extend the component to look like this:

<!-- products.vue -->
<template>
  <div>
    <h1>Products</h1>
    <img :src="img" alt="should work" />
  </div>
</template>
<script>
const url = require('~/assets/budapest.jpeg')

export default {
  data() {
    return {
      img: url
    }
  }
}
</script>

as you can see we need to import the resource to ensure we get the correct URL to our resource, like so:

const url = require('~/assets/budapest.jpeg')

Working with Style assets

You can use different approaches to styling in Nuxt like Sass, Scss, Less and CSS. For this example let's use scss.

To compile scss, we need some additional libraries. You need to run the following installation command in the terminal:

npm install node-sass sass-loader --save

This will give us the needed libraries so Nuxt can do the rest.

There are two ways we could be using scss now:

  1. Define styling in the component directly
  2. Create an external file and place in the assets directory

Define scss in the component

Let's start with defining the styles in the component directly, like so:

<!-- sample.vue -->
<template>
  <div class="images">
    add some nice images here
  </div>
</template>
<style lang="scss">
  .images {
    margin: 15px;
    padding: 20px;
    display: flex;
    justify-content: center;
    box-shadow: 0 0 10px grey;
  }
</style>

Nuxt will compile the above and apply it to any matching CSS classes.

Define an external file

The other way we can work with styling assets is by creating separate files.

Let's create the file page.scss under assets/scss with the following content:

.page {
  .title {
    font-size: 20px;
  }
}

NOTE, we can create the styling file directly under assets directory but I just like to separate concerns so I recommend a directory approach like so:

-| assets/
---| images/
---| scss/

We also need to point this out to Webpack so it finds it, so go and create a file called nuxt.config.js in the root and give it the following content:

module.exports = {
  css: [
    '@/assets/scss/page.scss'
  ]
}

Now our directory structure for the whole project should look something like so:

-| assets/
---| scss/
---| images/
-| pages/
-| nuxt.config.js
-| package.json

NOTE, nuxt.config.js is a configuration file that Nuxt will read from if it exists. There are a lot more you can do with nuxt.config.js and we have reason to come back to it.

Working with routing

ok, we understand how we can create different pages by simply creating them in the pages directory. How to move between pages though?

Simple, use <nuxt-link>

We get a lot of routing set up for free. So given the following file structure:

pages/
--| user/
-----| index.vue
-----| one.vue
--| index.vue

we would get routing set up like so:

router: {
  routes: [
    {
      name: 'index',
      path: '/',
      component: 'pages/index.vue'
    },
    {
      name: 'user',
      path: '/user',
      component: 'pages/user/index.vue'
    },
    {
      name: 'user-one',
      path: '/user/one',
      component: 'pages/user/one.vue'
    }
  ]
}

Dynamic routing

We should understand by now how our file structure affects the routing. There are more aspects of routing we need to understand though namely dynamic routing.

Consider the following file structure:

pages/
--| _slug/
-----| comments.vue
-----| index.vue
--| users/
-----| _id.vue
--| index.vue

We see the usage of underscore, _ in both the directory _slug and the Vue file _id.vue. This is how we create routes with parameters.

Let's look at the resulting routes:

router: {
  routes: [
    {
      name: 'index',
      path: '/',
      component: 'pages/index.vue'
    },
    {
      name: 'users-id',
      path: '/users/:id?',
      component: 'pages/users/_id.vue'
    },
    {
      name: 'slug',
      path: '/:slug',
      component: 'pages/_slug/index.vue'
    },
    {
      name: 'slug-comments',
      path: '/:slug/comments',
      component: 'pages/_slug/comments.vue'
    }
  ]
}

our file structure:

--| users/
-----| _id.vue

resulted in a route looking like this /users/:id?.

NOTE, the ? means that's it's optional if you want to make it mandatory you need the file structure to look like this:

--| users/
-----| _id/
---------| index.vue

Also

--| _slug/

resulted in /:slug

Validate route params

Now that we know how to deal with parameters in the routes, how do we validate those parameters?

We can add a validate() method for that. If it fails the check it will automatically route you to the 404 page.

export default {
  validate ({ params }) {
    // Must be a number
    return /^\d+$/.test(params.id)
  }
}

Nested routes

Sometimes you might have routes within your routes. You might have a /products route that in itself might render different pages depending on how the full route looks.

Let's say if we go to /products, it should load a product list but if it goes to /products/1, it should load a product detail. If we have this scenario it means we will have the following behavior:

  • a shell, this page can contain static and dynamic data and will need to contain a <nuxt-child/> component tag
  • a specific file structure

Let's have a look at the file structure:

pages/
--| products/
-----| _id.vue
-----| index.vue
--| products.vue

The above will treat products.vue as the shell page and it will generate the following routes:

router: {
  routes: [
    {
      path: '/products',
      component: 'pages/products.vue',
      children: [
        {
          path: '',
          component: 'pages/products/index.vue',
          name: 'products'
        },
        {
          path: ':id',
          component: 'pages/products/_id.vue',
          name: 'products-id'
        }
      ]
    }
  ]
}

To learn more about routing, check here:

https://nuxtjs.org/guide/routing

Working with async

When a request comes to a specific route we can bring in data asynchronously and use that to render the page. For that, we can use asyncData and fetch our data. Below we have a Vue component where asyncData are asking for data. It will block rendering until the data is fetched. We end by returning the data. The data we return ends up being amended to the data property of the component. As w can see in our <template> we are referring to article that was part of the data we returned from asyncData.

<template>
  <div v-if="article">
    <h3>
    {{article.title}}
    </h3>
    <div>
      {{article.description}}
    </div>
  </div>
  <div v-else>
    <h3>Sorry</h3>
    No article with that name 
    <strong>{{slug}}</strong>
  </div>
</template>
<script>
function getData(slug) {
  const content = {
    docker: {
      title: 'Docker 101',
      description: 'this is about Docker'
    },
    dotnet: {
      title: '.NET news',
      description: 'this is about .NET'
    }
  };
  return new Promise(resolve => {
    setTimeout(() => {
      resolve(content[slug]);
    }, 5000)
  })
}
export default {
  async asyncData ({ params }) {
    console.log('slug', params.slug);
    const res = await getData(params.slug)
    // called every time before loading the component
    return {
      article: res,
      slug: params.slug
    }
  }
}
</script>

Layout

For the layout we want to cover three cases:

  • default page, this is the page that constitutes the default rendering of a page unless you explicitly override it.
  • error page, we can specify a page that will take care of all erroneous responses.
  • custom layout, we will cover how to define a custom layout component and show how to use our custom layout

First off, let's create the directory layouts, like so:

---| layouts
---| pages

Default page

To create a default layout, simply create a component default.vue, like so:

---| layouts
-------| default.vue

Next, give it the following content:

<template>
  <div>
    <div class="header">Hello route demo</div>
    <div class="subheader">
      <div class="item">
        <nuxt-link to="/">Home page</nuxt-link>
      </div>
      <div class="item">
        <nuxt-link to="/products">Products</nuxt-link>
      </div>
    </div>
    <nuxt/>
  </div>
</template>
<style scoped>
</style>

In our template we create a header section with CSS class subheader, in it we have a number of <div> elements, each with a <nuxt-link> element, that's our navigational link.

We also render the <nuxt/> element, now this is important. This is the element that renders our page content, if you forget this page then it won't work properly.

Error page

We can create an error page that will allow us to capture all errors. Let's create the component error.vue, like so:

---| layouts
-------| error.vue

Give it the following content:

<template>
  <div class="container">
    <h1 v-if="error.statusCode === 404">Page not found</h1>
    <h1 v-else>An error occurred</h1>
    <nuxt-link to="/">Home page</nuxt-link>
  </div>
</template>
<script>
export default {
  props: ['error']
  // ,layout: 'blog' // you can set a custom layout for the error page
}
</script>

Note, how we have a input property error, like so props: ['error']. Additionally notehoow we can filter on status code and can render different messages depending on what the error is:

<h1 v-if="error.statusCode === 404">Page not found</h1>

Custom layout

Lastly, let's show how to create and apply a custom layout. You can name your custom layout component anything you want. We elect to name our component blog.vue, like so:

---| layouts
-------| blog.vue

Next let's give it some content, like so:

<template>
  <div class="blog">
    <h1>Here's the template for an article</h1>
    <nuxt class="page" />
  </div>
</template>

This looks just like default.vue in that we have a <nuxt> element somewhere to make sure we render the page content.

How do we use it?

Good question. Let's take a page component and set the layout property, like so:

<template>
  <div>
    <h3>Docker 101</h3>
    <div>
      {{content}}
    </div>
  </div>
</template>
<script>
export default {
  layout: 'blog',
  data() {
    return {
      content: 'something...'
    }
  }
}
</script>

Note, how we point out the layout: 'blog', thereby we refer to our layout by its name, minus the file extension.

Summary

That was quite a lot in one article. Guess what though, there's a lot more to learn.

Let's recap on our learnings, we learned:

  • The WHAT and WHY of Nuxt, it's important to understand the reason for wanting to use something. In the case of Nuxt, we learned that it had an opinionated architecture relying on convention. We also learned that it used a lot of great standard libraries for state management and server-side rendering.
  • Static site generation, we learned how we can address the SEO problem that most SPA apps suffer from.
  • How to create our Nuxt app in two ways, with a wizard and manually
  • Assets, we learned how to deal with assets, images as well as styles
  • Routing, then we covered routing, by convention based on our directory structures but also how to deal with dynamic routing
  • Async, then we learned how to use a method like asyncData() to read asynchronous data before rendering a page.
  • Layout, we learned how to create different layouts like default, error and a custom layout.

That was a lot but hopefully, you are now so comfortable with Nuxt that you see its value and can find out the rest you need in the docs.

Nuxt.js: a Minimalist Framework for Creating Universal Vue.js Apps

Nuxt.js: a Minimalist Framework for Creating Universal Vue.js Apps

In this article, you'll learn how we can take advantage of Nuxt.js to build server-rendered JavaScript applications with Vue.js. Learn how to use its generate command to generate static files for our pages, and deploy them quickly via a service like Firebase Hosting.

In this article, you'll learn how we can take advantage of Nuxt.js to build server-rendered JavaScript applications with Vue.js. Learn how to use its generate command to generate static files for our pages, and deploy them quickly via a service like Firebase Hosting.

Universal (or Isomorphic) JavaScript is a term that has become very common in the JavaScript community. It’s used to describe JavaScript code that can execute both on the client and the server.

Many modern JavaScript frameworks, like Vue.js, are aimed at building single-page applications (SPAs). This is done to improve the user experience and make the app seem faster, since users can see updates to pages instantaneously. While this has a lot of advantages, it also has a couple of disadvantages, such as long “time to content” when initially loading the app as the browser retrieves the JavaScript bundle, and some search engine web crawlers or social network robots won’t see the entire loaded app when they crawl your web pages.

Server-side rendering of JavaScript is about preloading JavaScript applications on a web server and sending rendered HTML as the response to a browser request for a page.

Building server-side rendered JavaScript apps can be a bit tedious, as a lot of configuration needs to be done before you even start coding. This is the problem Nuxt.js aims to solve for Vue.js applications.

What Nuxt.js Is

Simply put, Nuxt.js is a framework that helps you build server-rendered Vue.js applications easily. It abstracts most of the complex configuration involved in managing things like asynchronous data, middleware, and routing. It’s similar to Angular Universal for Angular, and Next.js for React.

According to the Nuxt.js docs, “its main scope is UI rendering while abstracting away the client/server distribution.”

Static Generation

Another great feature of Nuxt.js is its ability to generate static websites with the generate command. It’s pretty cool, and provides features similar to popular static generation tools like Jekyll.

Under the Hood of Nuxt.js

In addition to Vue.js 2.0, Nuxt.js includes the following: Vue-Router, Vuex (only included when using the store option), Vue Server Renderer and vue-meta. This is great, as it takes away the burden of manually including and configuring different libraries needed for developing a server-rendered Vue.js application. Nuxt.js does all this out of the box, while still maintaining a total size of 57kB min+gzip (60KB with vuex).

Nuxt.js also uses webpack with vue-loader and babel-loader to bundle, code-split and minify code.

How it works

This is what happens when a user visits a Nuxt.js app or navigates to one of its pages via <nuxt-link>:

  1. When the user initially visits the app, if the [nuxtServerInit](https://nuxtjs.org/guide/vuex-store/#the-nuxtserverinit-action "nuxtServerInit") action is defined in the store, Nuxt.js will call it and update the store.
  2. Next, it executes any existing middleware for the page being visited. Nuxt checks the nuxt.config.js file first for global middleware, then checks the matching layout file (for the requested page), and finally checks the page and its children for middleware. Middleware are prioritized in that order.
  3. If the route being visited is a dynamic route, and a validate() method exists for it, the route is validated.
  4. Then, Nuxt.js calls the asyncData() and fetch() methods to load data before rendering the page. The [asyncData()](https://nuxtjs.org/guide/async-data/ "asyncData()") method is used for fetching data and rendering it on the server-side, while the [fetch()](https://nuxtjs.org/api/pages-fetch/ "fetch()") method is used to fill the store before rendering the page.
  5. At the final step, the page (containing all the proper data) is rendered.

These actions are portrayed properly in this schema, gotten from the Nuxt docs:

Creating A Serverless Static Site With Nuxt.js

Let’s get our hands dirty with some code and create a simple static generated blog with Nuxt.js. We’ll assume our posts are fetched from an API and will mock the response with a static JSON file.

To follow along properly, a working knowledge of Vue.js is needed. You can check out Jack Franklin’s great getting started guide for Vue.js 2.0 if you’re new to the framework. I’ll also be using ES6 Syntax, and you can get a refresher on that here: sitepoint.com/tag/es6/.

Our final app will look like this:

The entire code for this article can be seen here on GitHub, and you can check out the demo here.

Application Setup and Configuration

The easiest way to get started with Nuxt.js is to use the template created by the Nuxt team. We can install it to our project (ssr-blog) quickly using the vue-cli:

vue init nuxt/starter ssr-blog


Once you’ve run this command, a prompt will open and ask you a couple of questions. You can press Return to accept the default answers, or enter values of your own.

Note: If you don’t have vue-cli installed, you have to run *npm install -g @vue/cli* first, to install it.

Next, we install the project’s dependencies:

cd ssr-blog
npm install


Now we can launch the app:

npm run dev


If all goes well, you should be able to visit http://localhost:3000 to see the Nuxt.js template starter page. You can even view the page’s source, to see that all content generated on the page was rendered on the server and sent as HTML to the browser.

Next, we can make some simple configurations in the nuxt.config.js file. We’ll add a few options:

// ./nuxt.config.js

module.exports = {
  /*
   * Headers of the page
   */
  head: {
    titleTemplate: '%s | Awesome JS SSR Blog',
    // ...
    link: [
      // ...
      {
        rel: 'stylesheet',
        href: 'https://cdnjs.cloudflare.com/ajax/libs/bulma/0.7.2/css/bulma.min.css'
      }
    ]
  },
  // ...
}


In the above config file, we simply specify the title template to be used for the application via the titleTemplate option. Setting the title option in the individual pages or layouts will inject the title value into the %s placeholder in titleTemplate before being rendered.

We also pulled in my current CSS framework of choice, Bulma, to take advantage of some preset styling. This was done via the link option.

Note: Nuxt.js uses vue-meta to update the headers and HTML attributes of our apps. So you can take a look at it for a better understanding of how the headers are being set.

Now we can take the next couple of steps by adding our blog’s pages and functionalities.

Working with Page Layouts

First, we’ll define a custom base layout for all our pages. We can extend the main Nuxt.js layout by updating the layouts/default.vue file:

<!-- ./layouts/default.vue -->

<template>
  <div>
    <!-- navigation -->
    <nav class="navbar has-shadow" role="navigation" aria-label="main navigation">
      <div class="container">
        <div class="navbar-start">
          <nuxt-link to="/" class="navbar-item">
            Awesome JS SSR Blog!
          </nuxt-link>
          <nuxt-link active-class="is-active" to="/" class="navbar-item is-tab" exact>Home</nuxt-link>
          <nuxt-link active-class="is-active" to="/about" class="navbar-item is-tab" exact>About</nuxt-link>
        </div>
      </div>
    </nav>
    <!-- /navigation -->

    <!-- displays the page component -->
    <nuxt/>

  </div>
</template>

<style>
  .main-content {
    margin: 30px 0;
  }
</style>


In our custom base layout, we add the site’s navigation header. We use the <nuxt-link> component to generate links to the routes we want to have on our blog. You can check out the docs on [<nuxt-link>](https://nuxtjs.org/api/components-nuxt-link "<nuxt-link>") to see how it works.

The <nuxt> component is really important when creating a layout, as it displays the page component.

It’s also possible to do a couple of more things — like define custom document templates and error layouts — but we don’t need those for our simple blog. I urge you to check out the Nuxt.js documentation on views to see all the possibilities.

Simple Pages and Routes

Pages in Nuxt.js are created as single file components in the pages directory. Nuxt.js automatically transforms every .vue file in this directory into an application route.

Building the Blog Homepage

We can add our blog homepage by updating the index.vue file generated by the Nuxt.js template in the pages directory:

<!-- ./pages/index.vue -->
<template>
  <div>
    <section class="hero is-medium is-primary is-bold">
      <div class="hero-body">
        <div class="container">
          <h1 class="title">
            Welcome to the JavaScript SSR Blog.
          </h1>
          <h2 class="subtitle">
            Hope you find something you like.
          </h2>
        </div>
      </div>
    </section>
  </div>
</template>

<script>
  export default {
    head: {
      title: 'Home'
    }
  }
</script>

<!-- Remove the CSS styles -->


As stated earlier, specifying the title option here automatically injects its value into the titleTemplate value before rendering the page.

We can now reload our app to see the changes to the homepage.

Building the About page

Another great thing about Nuxt.js is that it will listen to file changes inside the pages directory, so there’s no need to restart the application when adding new pages.

We can test this, by adding a simple about.vue page:

<!-- ./pages/about.vue -->
<template>
  <div class="main-content">
    <div class="container">
      <h2 class="title is-2">About this website.</h2>
      <p>Curabitur accumsan turpis pharetra <strong>augue tincidunt</strong> blandit. Quisque condimentum maximus mi, sit amet commodo arcu rutrum id. Proin pretium urna vel cursus venenatis. Suspendisse potenti. Etiam mattis sem rhoncus lacus dapibus facilisis. Donec at dignissim dui. Ut et neque nisl.</p>
      <br>
      <h4 class="title is-4">What we hope to achieve:</h4>
      <ul>
        <li>In fermentum leo eu lectus mollis, quis dictum mi aliquet.</li>
        <li>Morbi eu nulla lobortis, lobortis est in, fringilla felis.</li>
        <li>Aliquam nec felis in sapien venenatis viverra fermentum nec lectus.</li>
        <li>Ut non enim metus.</li>
      </ul>
    </div>
  </div>
</template>

<script>
export default {
  head: {
    title: 'About'
  }
}
</script>


Now, we can visit http://localhost:3000/about to see the about page, without having to restart the app, which is awesome.

Showing Blog Posts on the Homepage

Our current homepage is pretty bare as it is, so we can make it better by showing the recent blog posts from the blog. We’ll do this by creating a <posts> component and displaying it in the index.vue page.

But first, we have to get our saved JSON blog posts and place them in a file in the app root folder. The file can be downloaded from here, or you can just copy the JSON below and save in the root folder as posts.json:

[
    {
        "id": 4,
        "title": "Building universal JS apps with Nuxt.js",
        "summary": "Get introduced to Nuxt.js, and build great SSR Apps with Vue.js.",
        "content": "<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</p>",
        "author": "Jane Doe",
        "published": "08:00 - 07/06/2017"
    },
    {
        "id": 3,
        "title": "Great SSR Use cases",
        "summary": "See simple and rich server-rendered JavaScript apps.",
        "content": "<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</p>",
        "author": "Jane Doe",
        "published": "17:00 - 06/06/2017"
    },
    {
        "id": 2,
        "title": "SSR in Vue.js",
        "summary": "Learn about SSR in Vue.js, and where Nuxt.js can make it all faster.",
        "content": "<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</p>",
        "author": "Jane Doe",
        "published": "13:00 - 06/06/2017"
    },
    {
        "id": 1,
        "title": "Introduction to SSR",
        "summary": "Learn about SSR in JavaScript and how it can be super cool.",
        "content": "<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</p>",
        "author": "John Doe",
        "published": "11:00 - 06/06/2017"
    }
]


Note: Ideally the posts should be retrieved from an API or resource. For example, Contentful is a service that can be used for this.

Components live in the components directory. We’ll create the <posts> single file component in there:

<!-- ./components/Posts.vue -->
<template>
  <section class="main-content">
    <div class="container">
      <h1 class="title has-text-centered">
        Recent Posts.
      </h1>
      <div class="columns is-multiline">
        <div class="column is-half" v-for="post in posts" :key="post.id">
          <div class="card">
           <header class="card-header">
            <p class="card-header-title">
              {{ post.title }}
            </p>
          </header>
          <div class="card-content">
            <div class="content">
              {{ post.summary }}
              <br>
              <small>
                by <strong>{{ post.author}}</strong>
                \\ {{ post.published }}
              </small>
            </div>
          </div>
          <footer class="card-footer">
            <nuxt-link :to="`/post/${post.id}`"
              class="card-footer-item">
              Read More
            </nuxt-link>
          </footer>
        </div>
      </div>
    </div>
  </div>
</section>
</template>

<script>
  import posts from '~/posts.json'

  export default {
    name: 'posts',
    data () {
      return { posts }
    }
  }
</script>


We import the posts data from the saved JSON file and assign it to the posts value in our component. We then loop through all the posts in the component template with the v-for directive and display the post attributes we want.

Note: The *~* symbol is an alias for the */* directory. You can check out the docs here to see the different aliases Nuxt.js provides, and what directories they’re linked to.

Next, we add the <posts> component to the homepage:

<!-- ./pages/index.vue -->
<template>
<div>
    <!-- ... -->
    <posts />
</div>
</template>

<script>
import Posts from '~/components/Posts.vue'

export default {
  components: {
    Posts
  },
  // ...
}
</script>


Adding Dynamic Routes

Now we’ll add dynamic routes for the posts, so we can access a post for example with this URL: /post/1.

To achieve this, we add the post directory to the pages directory and structure it like this:

pages
└── post
    └── _id
        └── index.vue


This generates the corresponding dynamic routes for the application like this:

router: {
  routes: [
    // ...
    {
      name: 'post-id',
      path: '/post/:id',
      component: 'pages/post/_id/index.vue'
    }
  ]
}


Updating the single post file:

<!-- ./pages/post/_id/index.vue -->
<template>
  <div class="main-content">
    <div class="container">
      <h2 class="title is-2">{{ post.title }}</h2>
      <div v-html="post.content"></div>
      <br>
      <h4 class="title is-5 is-marginless">by <strong>{{ post.author }}</strong> at <strong>{{ post.published }}</strong></h4>
    </div>
  </div>
</template>

<script>
  // import posts saved JSON data
  import posts from '~/posts.json'

  export default {
    validate ({ params }) {
      return /^\d+$/.test(params.id)
    },
    asyncData ({ params }, callback) {
      let post = posts.find(post => post.id === parseInt(params.id))
      if (post) {
        callback(null, { post })
      } else {
        callback({ statusCode: 404, message: 'Post not found' })
      }
    },
    head () {
      return {
        title: this.post.title,
        meta: [
          {
            hid: 'description',
            name: 'description',
            content: this.post.summary
          }
        ]
      }
    }
  }
</script>


Nuxt.js adds some custom methods to our page components to help make the development process easier. See how we use some of them on the single post page:

  • Validate the route parameter with the validate method. Our validate method checks if the route parameter passed is a number. If it returns false, Nuxt.js will automatically load the 404 error page. You can read more on it here.
  • The asyncData method is used to fetch data and render it on the server side before sending a response to the browser. It can return data via different methods. In our case, we use a callback function to return the post that has the same id attribute as the route id parameter. You can see the various ways of using this function here.
  • As we’ve seen before, we use the head method to set the page’s headers. In this case, we’re changing the page title to the title of the post, and adding the post summary as a meta description for the page.

Great, now we can visit our blog again to see all routes and pages working properly, and also view the page source to see the HTML being generated. We have a functional server-rendered JavaScript application.

Generating Static Files

Next, we can generate the static HTML files for our pages.

We’ll need to make a minor tweak though, as by default Nuxt.js ignores dynamic routes. To generate the static files for dynamic routes, we need to specify them explicitly in the ./nuxt.config.js file.

We’ll use a callback function to return the list of our dynamic routes:

// ./nuxt.config.js

module.exports = {
  // ...
  generate: {
    routes(callback) {
      const posts = require('./posts.json')
      let routes = posts.map(post => `/post/${post.id}`)
      callback(null, routes)
    }
  }
}


You can check here for the full documentation on using the generate property.

To generate all the routes, we can now run this command:

npm run generate


Nuxt saves all generated static files to a dist folder.

Deployment on Firebase Hosting

As a final step, we can take advantage of hosting by Firebase to make our static website live in a couple of minutes. This step assumes that you have a Google account.

First, install the Firebase CLI, if you don’t already have it:

npm install -g firebase-tools


To connect your local machine to your Firebase account and obtain access to your Firebase projects, run the following command:

firebase login


This should open a browser window and prompt you to sign in. Once you’re signed in, visit https://console.firebase.google.com and click Add project. Make the relevant choices in the wizard that opens.

Once the project is created, go to the project’s hosting page at [https://console.firebase.google.com/project/<project](https://console.firebase.google.com/project/<project "https://console.firebase.google.com/project/<project") name>/hosting and complete the Get started wizard.

Then, on your PC, from the root of your project directory, run the following command:

firebase init


In the wizard that appears, select “Hosting”. Then select your newly created project from the list of options. Next choose the dist directory as the public directory. Select to configure the page as a single-page app and finally select “No” when asked if you want to overwrite dist/index.html.

Firebase will write a couple of configuration files to your project, then put the website live at [https://<project](https://<project "https://<project") name>.firebaseapp.com. The demo app for this article can be seen at nuxt-ssr-blog.firebaseapp.com.

If you run into problems, you can find full instructions on Firebase’s quickstart page.

Conclusion

In this article, we’ve learned how we can take advantage of Nuxt.js to build server-rendered JavaScript applications with Vue.js. We also learned how to use its generate command to generate static files for our pages, and deploy them quickly via a service like Firebase Hosting.

The Nuxt.js framework is really great. It’s even recommended in the official Vue.js SSR GitBook. I really look forward to using it in more SSR projects and exploring all of its capabilities.

How to add Authentication to Nuxt.JS and Vue.JS

How to add Authentication to Nuxt.JS and Vue.JS

This Vue.JS Tutorial shows how to add Authentication and Authorization to your NuxtJS App and make it work with SSR

This VueJS Tutorial shows how to add Authentication and Authorization to your NuxtJS app, and make it work with SSR (server-side rendering). Once you understand the concepts and flow, it become surprisingly easy.

For this introduction to the Nuxt Auth module, we don’t require that you’ve watched any of the previous videos on this channel, but to get the most out of it you do need to have a working Nuxt app and basic knowledge of both Nuxt and Vue.

0:00 Start
3:57 Installing Nuxt Auth and using $auth.user
8:23 Login and Register forms
13:45 Configuring and using loginWith()
27:52 Error Handling and User Notifications
34:11 Auth Middleware
40:51 Conclusion

Referenced Videos

The video where we created the UserAuthForm: https://youtu.be/5kVThw0GQv4