You are reading Edgio Applications v5 docs. Check out our latest docs for Edgio Applications v7.


This guide shows you how to deploy a Nuxt.js application to Edgio. If you run into any issues please consult the Troubleshooting section.

Example SSR Site

This Nuxt.js example app uses server-side rendering and prefetching to provide lightening-fast transitions between pages.

Example ISG Site

This Nuxt.js example app uses ISG (Incremental Static Generation) to provide lightening-fast transitions between pages.


This framework has a connector developed for Edgio. See Connectors for more information.


Before proceeding, you will need an Edgio property. Create one now if you do not already have one.
Learn how to create a property.

System Requirements

Sign up for Edgio

Deploying requires an account on Edgio. Sign up here for free.

Install the Edgio CLI

If you have not already done so, install the Edgio CLI.
1npm i -g @edgio/cli@^5.0.0

Creating a new Nuxt app

If you don’t already have a nuxt.js application, you can create one using:
1npm create nuxt-app my-nuxt-app
Nuxt’s create module will ask you a series of questions to configure your app. Make sure you answer as follows:
  • For Choose rendering mode select Universal (SSR)
  • Your answers to the other questions should not matter for the purposes of this guide.

Adding Edgio to an existing Nuxt app

To prepare your Nuxt.js application for Edgio:
  1. In the existing nuxt.config.js configuration, add “@edgio/nuxt/module” to buildModules:
1// nuxt.config.js
3module.exports = {
4 ...
5 buildModules: [['@edgio/nuxt/module', { edgioSourceMaps: true }]],
6 ...
  • edgioSourceMaps: true|false: when true, the serverless build includes sourcemap files which make debugging easier when tailing the server logs in the Edgio Developer console. It also increases the serverless bundle size, which may push your deployments over the 50MB (compressed) limit.
We noticed some performance issues related to sourcemaps being loaded in our Serverless infrastructure, which may result in 539 project timeout errors. In case you encounter such errors, please try again with sourcemaps disabled. This document will be updated once the problem is fully resolved.
  1. Run edgio init to configure your project for Edgio.
1edgio init --edgioVersion ^5.0.0
The edgio init command will automatically add all the required dependencies and files to your project. These include:
  • The @edgio/core package
  • The @edgio/nuxt package
  • The @edgio/vue package
  • edgio.config.js - Contains various configuration options for Edgio.
  • routes.js - A default routes file that sends all requests to nuxt.js. You can update this file to add caching or proxy some URLs to a different origin as described later in this guide.
  • sw/service-worker.js - A service worker that provides static asset and API prefetching.
This command will also update your package.json with the following changes:
  • Moves all packages in dependencies to devDependencies except those listed in the modules property of nuxt.config.js.
  • Adds @nuxt/core to dependencies
  • Adds several scripts to run the available edgio commands
As an example, here’s the original package.json from Nuxt’s create step:
2 "name": "my-nuxt-app",
3 "version": "1.0.0",
4 "description": "My remarkable Nuxt.js project",
5 "author": "Techy Ted",
6 "private": true,
7 "scripts": {
8 "dev": "nuxt",
9 "build": "nuxt build",
10 "start": "nuxt start",
11 "generate": "nuxt generate"
12 },
13 "dependencies": {
14 "@edgio/cli": "^2.0.0",
15 "@edgio/core": "^2.0.0",
16 "@edgio/nuxt": "^2.0.0",
17 "nuxt": "^2.0.0"
18 },
19 "devDependencies": {}
And here is the package.json after modifications by edgio init:
2 "name": "my-nuxt-app",
3 "version": "1.0.0",
4 "description": "My remarkable Nuxt.js project",
5 "author": "Techy Ted",
6 "private": true,
7 "scripts": {
8 "dev": "edgio run",
9 "build": "edgio build",
10 "start": "edgio run",
11 "prod": "edgio run --production",
12 "generate": "nuxt generate"
13 },
14 "dependencies": {
15 "@nuxt/core": "^2.14.2"
16 },
17 "devDependencies": {
18 "@edgio/cli": "^2.0.0",
19 "@edgio/core": "^2.0.0",
20 "@edgio/nuxt": "^2.0.0",
21 "@edgio/vue": "^2.0.0",
22 "dotenv": "^8.2.0",
23 "nuxt": "^2.0.0",
24 "serverless": "^1.64.0",
25 "serverless-dotenv-plugin": "^2.3.2",
26 "serverless-offline": "^5.14.1"
27 }

Run the Nuxt.js app locally on Edgio

Run the Nuxt.js app with the command:
1npm run edgio:dev
Load the site:

modules vs buildModules

Nuxt does not bundle packages listed in the modules property of nuxt.config.js when building your app for production. This can lead to an increased bundle size and slow down server-side rendering. Most Nuxt modules can be moved to buildModules. We recommend the following to maximize performance of server-side rendering in the cloud:
  • Move all entries from modules to buildModules in nuxt.config.js
  • Move all corresponding packages from dependencies to devDependencies in package.json
  • Run yarn install or npm install to update your lock file.
Doing so will exclude these modules from your production deployment and keep the bundle size as small as possible.


The next few sections of this guide explain how Edgio interacts with Nuxt’s routing, which is important if you are migrating an existing application. If you just created a new nuxt app, you can jump to Running Locally and come back to these sections later. Edgio supports Nuxt.js’s built-in routing scheme. The default routes.js file created by edgio init sends all requests to Nuxt.js via a fallback route:
1// This file was added by edgio init.
2// You should commit this file to source control.
4const {Router} = require('@edgio/core/router');
5const {nuxtRoutes, renderNuxtPage} = require('@edgio/nuxt');
7module.exports = new Router().use(nuxtRoutes);

nuxtRoutes Middleware

In the code above, nuxtRoutes adds all Nuxt.js routes based on the /pages directory. It’s also compatible with extending Nuxt’s router via the router config in nuxt.config.js, for example:
1// nuxt.config.js
2export default {
3 // ... more config ...
4 router: {
5 // For example, we can extend the nuxt router to accept /products in addition to /p.
6 // The nuxtRoutes middleware automatically picks this up and adds it to the Edgio router
7 extendRoutes(routes, resolve) {
8 routes.push({
9 path: '/products/:id?',
10 component: resolve(__dirname, 'pages/p/_id.vue'),
11 });
12 },
13 },
14 // ... more config ...
You can add additional routes before and after nuxtRoutes, for example to send some URLs to an alternate backend. This is useful for gradually replacing an existing site with a new Nuxt.js app.
A popular use case is to fallback to a legacy site for any route that your Nuxt.js app isn’t configured to handle:
1export default new Router()
2 .use(nuxtRoutes)
3 .match('/:path*', ({proxy}) => proxy('legacy'));
To configure the legacy backend, use edgio.config.js:
1module.exports = {
2 backends: {
3 legacy: {
4 domainOrIp: process.env.LEGACY_BACKEND_DOMAIN || '',
5 hostHeader:
6 process.env.LEGACY_BACKEND_HOST_HEADER || '',
7 },
8 },
Using environment variables here allows you to configure different legacy domains for each Edgio environment.


The easiest way to add edge caching to your nuxt.js app is to add caching routes before the middleware. For example, imagine you have /pages/c/_categoryId.js:
1export default new Router()
2 .get('/pages/c/:categoryId', ({cache}) => {
3 cache({
4 browser: {
5 maxAgeSeconds: 0,
6 serviceWorkerSeconds: 60 * 60 * 24,
7 },
8 edge: {
9 maxAgeSeconds: 60 * 60 * 24,
10 staleWhileRevalidateSeconds: 60 * 60,
11 },
12 });
13 })
14 .use(nuxtRoutes);


The @edgio/nuxt/module builds a service worker that enables prefetching using Edgio and injects it into your app’s browser code. The service worker is based on Google’s Workbox library. The entry point for the service worker source code is sw/service-worker.js. If your app has an existing service worker that uses workbox, you can copy its contents into sw/service-worker.js and simply add the following to your service worker:
1import {Prefetcher} from '@edgio/prefetch/sw';
2new Prefetcher().route();
The above allows you to prefetch pages from Performance’s cache to greatly improve browsing speed. To prefetch a page, add the Prefetch component from @edgio/vue to any router-link or nuxt-link element:
2 <ul v-for="product in products">
3 <li>
4 <Prefetch v-bind:url="'/api/' + product.url">
5 <nuxt-link v-bind:to="product.url">
6 <img v-bind:src="product.thumbnail" />
7 </nuxt-link>
8 </Prefetch>
9 </li>
10 </ul>
13 import { Prefetch } from '@edgio/vue'
14 export default {
15 components: {
16 Prefetch,
17 },
18 }
The Prefetch component fetches data for the linked page from Performance’s cache based on the url property and adds it to the service worker’s cache when the link becomes visible in the viewport. When the user taps on the link, the page transition will be instantaneous because the browser won’t need to fetch data from the network.

Serving Sitemap with SSR

You can configure Nuxt to generate a sitemap in SSR mode with the following configuration:
1export default {
2 ...
4 // Modules:
5 modules: [
6 '@nuxtjs/sitemap',
7 ],
9 sitemap: {
10 hostname: '',
11 path: '/sitemap.xml',
12 defaults: {
13 lastmod: new Date(),
14 changefreq: 'weekly',
15 priority: 0.8,
16 },
17 },
Within the Edgio router, add the following:
1.match('/sitemap.xml', ({ renderWithApp }) => {
2 renderWithApp()
This will send all traffic for /sitemap.xml to Nuxt middleware for server-side rendering.

Static Sites

Edgio supports fully and partially static sites using Nuxt generate. To deploy a static Nuxt site on Edgio, simply set target: 'static' in nuxt.config.js and run edgio deploy. This will run nuxt build and nuxt generate to generate a static version of your site.

Incremental Static Rendering (ISG)

By default, requests for any pages that are not statically rendered at build time will fall back to server side rendering. If you use the Edgio router to cache pages that are not statically rendered, the first user who attempts to access the page will see the fallback HTML page generated by Nuxt (200.html by default). Edgio will render and cache the HTML in the background so that subsequent visits result in a full HTML response. This behavior is similar to Next.js incremental static rendering (ISG). Here is an example route that adds caching for a partially static page:
1import {nuxtRoutes} from '@edgio/nuxt';
2import {Router} from '@edgio/core/router';
4export default new Router()
5 .get('/products/:id', ({cache}) => {
6 cache({
7 edge: {
8 // Requests for product pages that are not statically generated will fall back to SSR.
9 // The first user will see the 200.html loading page generated by Nuxt.
10 // Edgio will render full HTML response in the background and cache it for one hour at the edge.
11 // All future requests to the page will result in the full HTML response.
12 maxAgeSeconds: 60 * 60 * 24,
13 staleWhileRevalidateSeconds: 60 * 60, // continue to serve stale responses from the edge cache while refreshing via SSR in the background
14 },
15 });
16 })
17 .use(nuxtRoutes);

Rendering a 404 Page

If you set the fallback property in the generate config to true, Nuxt.js will generate a 404.html page that will be served whenever the URL does not match a static page. Edgio will send a 404 http status for these URLs. Note that if you set the fallback property to a string, Nuxt will generate a fallback page with that name, and Edgio will serve it with a 200 http status when the URL does not match a statically generated page.


Nuxt requires that certain resources are included in a build and deploy to have access to them. As such, at times this will require additional configuration. To include additional resources for server side rendering, API calls, etc., use the includeFiles option in your edgio.config.js file. Read more
In this example, we would have an api folder that we want to include all items from.
1module.exports = {
2 includeFiles: {
3 'api/**/*': true,
4 },
In addition, if includeNodeModules does not copy over the necessary package that may be needed in production, it can be included via this key as well. For instance,
1module.exports = {
2 includeFiles: {
3 'node_modules/some_package/**/*': true,
4 },


The Nuxt team provides a renderer called Nitro which optimizes your application for serverless deployment and greatly minimizes the size of your server application bundle. If you’re running into the size limitation for serverless bundles (50MB), you might try adding Nitro to your app. As of June 2021 Nitro is still not production ready, so use at your own risk.
Edgio provides a connector specifically for Nuxt apps that use nitro called @edgio/nuxt-nitro.
To add Nitro to your app, make the following changes:
  1. Install nitro and the connector as dev dependencies:
1npm install -D @nuxt/nitro @edgio/nuxt-nitro`
  1. Ensure buildModules in nuxt.config.js contains the following:
1buildModules: [
2 '@nuxt/nitro/compat',
3 '@edgio/nuxt-nitro/module', // If you have previously added @edgio/nuxt/module you can remove it.
4 // ...others...
  1. Add the following to nuxt.config.js:
1publicRuntimeConfig: {
2 nitroVersion: require('@nuxt/nitro/package.json').version,
  1. If your nuxt.config.js has a target property, remove it.
  2. If you’ve previously added @edgio/nuxt as a dependency, you can remove it.

Additional Nitro Resources

Running Locally

Test your app with Sites on your local machine by running the following command in your project’s root directory:
1edgio build && edgio run
You can do a production build of your app and test it locally using:
1edgio build && edgio run --production
Setting --production runs your app exactly as it will be uploaded to the Edgio cloud using serverless-offline.


Deploy your app to the Sites by running the following command in your project’s root directory:
1edgio deploy
See Deployments for more information.


The following section describes common gotchas and their workarounds.

I get an error message Nuxt.js Internal Server Error

This may be because you have a custom server framework (such as Express). Please make sure you selected None when asked to choose Choose custom server framework during the creation of your nuxt app.

edgio init doesn’t work

If you get a command not found error such as:
1edgio init
2- bash: edgio: command not found
Make sure you installed the Edgio CLI
1npm i -g @edgio/cli@^5.0.0

Make sure your version of the Edgio CLI is current

If you previously installed the Edgio CLI, make sure your version is current.
Check npm for the latest released version of the CLI:
1npm show @edgio/cli version
Compare the latest release against the version currently installed on your system:
1edgio --version
If your version is out of date you can update it by running
1npm update -g @edgio/cli

Error on deploy: edgio-deploy-lambda: Unzipped size must be smaller than...

As the error states, there is an upper limit on how big a package can be when deployed to our serverless infrastructure. Some common strategies for solving:
  • You may need to move some dependencies as described here. Only dependencies are copied up to the lambda.
  • Make sure you are using imports in a smart way. A common example is changing: import { get } from lodash to import get from lodash/get to avoid unnecessary bloat in your modules
You can view what is included in your package under .edgio/lambda/ after a build, and running du -h -d 1 on the directories in a shell will output the size of each directory and help you identify where space savings can be found, ie du -h -d 1 .edgio/lambda/.nuxt