chore: v2.13.0 (#1922)

* chore: update plugins

* docs: update generate.ignore

* ko: api translations added (#1944)

* Create components-client-only.md

* Create configuration-builddir.md

* Create configuration-cli.md

* Create configuration-dir.md

* Create $nuxt.md

* Create configuration-extend-plugins.md

* chore: simplify installation

* feat: add components option

* fix: correct meta description

* docs: add telemetry configuration

* docs: update typo

* docs: generate updated

* docs: export command

* docs: add export to commands

* docs: remove cross-env

* docs: update export command

* docs: remove cross env

* docs: update mode add target page

* docs: link mode and target

* docs: add target to menu

* docs: default server for target

* docs: target explanation

* docs: target explanation

* docs: add target to commands

* docs: update usage for context 👀

* docs: fixes after meeting

* docs: fix commands

* docs: improve commands

* docs: improve crawler explanation

* docs: runtimeConfig

* docs: improvements on api

* fix: link to article

* fix: link to article

* docs: improvements on runtimeConfig

* blog: going full static

* blog: env post

* fix: link

* fix: link in blog

* docs: update routes

* blog: update description full static

* docs: add video

* focs: fix typo

* docs: 2.13

Co-authored-by: ESnark <31977180+ESnark@users.noreply.github.com>
Co-authored-by: debs-obrien <debs_obrien@yahoo.co.uk>
Co-authored-by: Pooya Parsa <pyapar@gmail.com>

Author: 4 people

de/api/configuration-dev.md

@@ -13,7 +13,7 @@ description: Define the development or production mode.
 This property is overwritten by [nuxt commands](/guide/commands):
 
 - `dev` is forced to `true` with `nuxt`
-- `dev` is forced to `false` with `nuxt build`, `nuxt start` and `nuxt generate`
+- `dev` is forced to `false` with `nuxt build`, `nuxt start`, `nuxt generate` and `nuxt export`.
 
 This property should be used when using [Nuxt.js programmatically](/api/nuxt):
 

de/api/configuration-generate.md

@@ -9,14 +9,14 @@ description: Configure the generation of your universal web application to a sta
 
 > Configure the generation of your universal web application to a static web application.
 
-When launching `nuxt generate` or calling `nuxt.generate()`, Nuxt.js will use the configuration defined in the `generate` property.
+When launching `nuxt export` or `nuxt generate` or calling `nuxt.generate()`, Nuxt.js will use the configuration defined in the `generate` property.
 
 ## dir
 
 - Type: `String`
 - Default: `'dist'`
 
-Directory name created by `nuxt generate`.
+Directory name created by `nuxt export` or nuxt `generate`.
 
 ## fallback
 
@@ -66,7 +66,9 @@ You can change the default configuration of [html-minifier](https://github.com/k
 
 - Type: `Array`
 
-[Dynamic routes](/guide/routing#dynamic-routes) are ignored by the `generate` command.
+As of Nuxt v2.13 there is a crawler installed that will now crawl your link tags and generate your routes when using the command `nuxt export` based on those links. 
+
+[Dynamic routes](/guide/routing#dynamic-routes) are ignored by the `generate` command when using Nuxt <= v2.12.
 
 Example:
 
@@ -201,7 +203,7 @@ async asyncData ({ params, error, payload }) {
 - Type: `Boolean`
 - Default: `true`
 
-By default, running `nuxt generate` will create a directory for each route & serve an `index.html` file.
+By default, running `nuxt export` or `nuxt generate` will create a directory for each route & serve an `index.html` file.
 
 Example:
 

de/api/context.md

@@ -12,16 +12,16 @@ List of all the available keys in `context`:
 | `app`                  | Root Vue Instance                                                                  | Client & Server | The root Vue instance that includes all your plugins. For example, when using `axios`, you can get access to `$axios` through `context.app.$axios`.                                                                                                                                         |
 | `isClient`             | `Boolean`                                                                          | Client & Server | Boolean to let you know if you're actually renderer from the client-side (_deprecated._ use `process.client`).                                                                                                                                                                              |
 | `isServer`             | `Boolean`                                                                          | Client & Server | Boolean to let you know if you're actually renderer from the server-side (_deprecated._ use `process.server`).                                                                                                                                                                              |
-| `isStatic`             | `Boolean`                                                                          | Client & Server | Boolean to let you know if you're actually inside a generated app (via `nuxt generate`).                                                                                                                                                                                                    |
+| `isStatic`             | `Boolean`                                                                          | Client & Server | Boolean to let you know if you're actually inside a generated app (via `nuxt export` or `nuxt generate`).                                                                                                                                                                                                    |
 | `isDev`                | `Boolean`                                                                          | Client & Server | Boolean to let you know if you're in dev mode, can be useful for caching some data in production.                                                                                                                                                                                           |
 | `isHMR`                | `Boolean`                                                                          | Client & Server | Boolean to let you know if the method/middleware is called from webpack hot module replacement (*only on client-side in dev mode*).                                                                                                                                                         |
 | `route`                | [Vue Router Route](https://router.vuejs.org/en/api/route-object.html)              | Client & Server | Vue Router route instance.                                                                                                                                                                                                                                                                  |
 | `store`                | [Vuex Store](https://vuex.vuejs.org/en/api.html#vuexstore-instance-properties)     | Client & Server | Vuex Store instance. **Available only if the [vuex store](/guide/vuex-store) is set**.                                                                                                                                                                                                      |
 | `env`                  | `Object`                                                                           | Client & Server | Environment variables set in `nuxt.config.js`, see [env api](/api/configuration-env).                                                                                                                                                                                                       |
 | `params`               | `Object`                                                                           | Client & Server | Alias of `route.params`.                                                                                                                                                                                                                                                                    |
 | `query`                | `Object`                                                                           | Client & Server | Alias of `route.query`.                                                                                                                                                                                                                                                                     |
-| `req`                  | [`http.Request`](https://nodejs.org/api/http.html#http_class_http_incomingmessage) | Server          | Request from the Node.js server. If Nuxt is used as a middleware, the req object might be different depending of the framework you're using.<br>**Not available via `nuxt generate`**.                                                                                                      |
-| `res`                  | [`http.Response`](https://nodejs.org/api/http.html#http_class_http_serverresponse) | Server          | Response from the Node.js server. If Nuxt is used as a middleware, the res object might be different depending of the framework you're using.<br>**Not available via `nuxt generate`**.                                                                                                     |
+| `req`                  | [`http.Request`](https://nodejs.org/api/http.html#http_class_http_incomingmessage) | Server          | Request from the Node.js server. If Nuxt is used as a middleware, the req object might be different depending of the framework you're using.<br>**Not available via `nuxt export` or `nuxt generate`**.                                                                                                      |
+| `res`                  | [`http.Response`](https://nodejs.org/api/http.html#http_class_http_serverresponse) | Server          | Response from the Node.js server. If Nuxt is used as a middleware, the res object might be different depending of the framework you're using.<br>**Not available via `nuxt export` or `nuxt generate`**.                                                                                                     |
 | `redirect`             | `Function`                                                                         | Client & Server | Use this method to redirect the user to another route, the status code is used on the server-side, default to `302`. `redirect([status,] path [, query])`.                                                                                                                                  |
 | `error`                | `Function`                                                                         | Client & Server | Use this method to show the error page: `error(params)`. The `params` should have the properties `statusCode` and `message`.                                                                                                                                                                |
 | `nuxtState`            | `Object`                                                                           | Client          | Nuxt state, useful for plugins which uses `beforeNuxtRender` to get the nuxt state on client-side before hydration. **Available only in `universal` mode**.                                                                                                                                 |

de/faq/github-pages.md

@@ -57,6 +57,15 @@ module.exports = {
 
 and now we just need to set `DEPLOY_ENV='GH_PAGES'` to build the site for GitHub Pages:
 
+For Nuxt >= v2.13
+```js
+/* package.json */
+"scripts": {
+  "build:gh-pages": "DEPLOY_ENV=GH_PAGES nuxt build",
+  "generate:gh-pages": "DEPLOY_ENV=GH_PAGES nuxt build && nuxt export"
+},
+```
+For Nuxt <= v2.12
 ```js
 /* package.json */
 "scripts": {
@@ -90,6 +99,18 @@ npm install push-dir --save-dev
 
 Add a `deploy` command to your `package.json` with the branch as `gh-pages` for project repository OR `master` for user or organization site.
 
+For Nuxt >= v2.13
+```js
+"scripts": {
+  "dev": "nuxt",
+  "build": "nuxt build",
+  "start": "nuxt start",
+  "generate": "nuxt build && nuxt export",
+  "deploy": "push-dir --dir=dist --branch=gh-pages --cleanup"
+},
+```
+
+For Nuxt <= v2.12
 ```js
 "scripts": {
   "dev": "nuxt",

de/faq/netlify-deployment.md

@@ -7,7 +7,7 @@ description: How to deploy Nuxt.js on Netlify?
 
 Deploying to [Netlify](https://www.netlify.com) is a low friction option for getting a __statically generated__ Nuxt.js site online quickly.
 
-The core of the process leverages the `nuxt generate` command during deployment to build a static version of your Nuxt.js app into a `dist` directory. The contents of this directory are then deployed to a production URL.
+The core of the process leverages the `nuxt build && nuxt export`(>= v2.13) or `nuxt generate`(<= v2.12) command during deployment to build a static version of your Nuxt.js app into a `dist` directory. The contents of this directory are then deployed to a production URL.
 
 ## Getting Started
 
@@ -21,6 +21,6 @@ Press the _"New site from Git"_ button on the Netlify dashboard. Authenticate wi
 
 > Optionally, you can add additional ENV variables via the _"Advanced"_ button. These can be helpful for swapping in alternative API credentials and so on. Netlify also provides a [default ENV variables](https://www.netlify.com/docs/build-settings/#build-environment-variables) which can be read by your Nuxt.js application at build time.
 
-Click _"Deploy site"_ to immediately trigger a deploy. Your Netlify site will be assigned a random URL and deployed using the `nuxt generate` command.
+Click _"Deploy site"_ to immediately trigger a deploy. Your Netlify site will be assigned a random URL and deployed using the `nuxt build && nuxt export`(>= v2.13) or `nuxt generate`(<= v2.12) command.
 
 Voilà! Your Nuxt.js application is now hosted on Netlify!

de/faq/surge-deployment.md

@@ -29,7 +29,9 @@ surge dist/
 
 Done :)
 
-If you have a project with [dynamic routes](/guide/routing#dynamic-routes), take a look at the [`generate` configuration](/api/configuration-generate) to tell Nuxt.js how to generate these dynamic routes.
+If you have a project with [dynamic routes](/guide/routing#dynamic-routes), take a look at the [`generate` configuration](/api/configuration-generate) to tell Nuxt.js how to generate these dynamic routes if you are using Nuxt <= v2.12. 
+
+If you are using Nuxt >= 2.13 then a crawler has been installed tht will crawl your link tags and generate the dynamic routes based on these links when using the command `nuxt build && nuxt export`.
 
 <div class="Alert">
 

de/guide/commands.md

@@ -88,24 +88,47 @@ Note: we recommend putting `.nuxt` in `.npmignore` or `.gitignore`.
 Nuxt.js gives you the ability to host your web application on any static hosting.
 
 To generate our web application into static files:
+For Nuxt >= 2.13:
+```json
+"scripts": {
+    "generate": "nuxt build && nuxt export"
+  } 
+```
+For Nuxt <= 2.12:
+```json
+"scripts": {
+    "generate": "nuxt generate"
+  } 
+```
+
 
 ```bash
 npm run generate
 ```
 
 It will create a `dist` folder with everything inside ready to be deployed on a static hosting site.
 
-If you have a project with [dynamic routes](/guide/routing#dynamic-routes), take a look at the [generate configuration](/api/configuration-generate) to tell Nuxt.js how to generate these dynamic routes.
+<div class="Alert Alert-blue">
+
+As of Nuxt v2.13 there is a crawler installed that will now crawl your link tags and generate your routes when using the command `nuxt build && nuxt export` based on those links. 
+
+</div>
+
+<div class="Alert Alert--orange">
+
+**Warning:** dynamic routes are ignored by the `generate` command when using Nuxt <= v2.12: [API Configuration generate](/api/configuration-generate#routes)
+
+</div>
 
 <div class="Alert">
 
-When generating your web application with `nuxt generate`, [the context](/api/context) given to [data()](/guide/async-data#the-data-method) and [fetch()](/guide/vuex-store#the-fetch-method) will not have `req` and `res`.
+When generating your web application with `nuxt build && nuxt export` or `nuxt generate`, [the context](/api/context) given to [data()](/guide/async-data#the-data-method) and [fetch()](/guide/vuex-store#the-fetch-method) will not have `req` and `res`.
 
 </div>
 
 ### Single Page Application Deployment (SPA)
 
-`nuxt generate` still needs SSR engine during build/generate time while having the advantage of having all our pages pre rendered, and have a high SEO and page load score. The content is generated at *build time*. For example, we can't use it for applications where content depends on user authentication or a real time API (at least for the first load).
+`nuxt build && nuxt export` or `nuxt generate` still need the SSR engine during build/generate time while having the advantage of having all our pages pre rendered, and have a high SEO and page load score. The content is generated at *build time*. For example, we can't use it for applications where content depends on user authentication or a real time API (at least for the first load).
 
 The SPA idea is simple! When SPA mode is enabled using `mode: 'spa'` or `--spa` flag, and we run build, generation automatically starts after the build. This generation contains common meta and resource links, but not page content.
 

de/guide/index.md

@@ -73,7 +73,7 @@ If you already have a server, you can plug Nuxt.js by using it as a middleware.
 
 ## Static Generated (Pre Rendering)
 
-The big innovation of Nuxt.js comes with the `nuxt generate` command.
+The big innovation of Nuxt.js comes with the `nuxt build && nuxt export` command for Nuxt >= v2.13 or `nuxt generate` command for Nuxt <= v2.12.
 
 When building your application, it will generate the HTML for every one of your routes and store it in a file.
 
@@ -105,15 +105,31 @@ We don't want to manually generate the application every time we update the [doc
 
 1. Clones the [nuxtjs.org repository](https://github.com/nuxt/nuxtjs.org)
 2. Installs the dependencies via `npm install`
-3. Runs `nuxt generate`
+3. Runs `nuxt build && nuxt export`(>= v2.13) or `nuxt generate`(<= v2.12)
 4. Pushes the `dist` folder to the `gh-pages` branch
 
 We now have a **Serverless Static Generated Web Application** :)
 
-We can go further by thinking of an e-commerce web application made with `nuxt generate` and hosted on a CDN. Everytime a product is out of stock or back in stock, we regenerate the web app. But if the user navigates through the web app in the meantime, it will be up to date thanks to the API calls made to the e-commerce API. No need to have multiple instances of a server + a cache anymore!
+The new full static module which is available since v2.13 generates your html and static assets at build time which means everything is already generated and therefore not only is it great for SEO but it can also be hosted for free on any of the static hosting providers. 
+
+Nuxt v2.13 also comes with a crawler installed which will crawl your link tags and generate your dynamic routes based on these links which means there is no need to manually generate your dynamic links anymore.
+
+The static target works by saving the calls to your API in payload.js files in a static folder. These payloads are then cached for better performance and offline support and as your API is not called on client side navigation any more (when called using asyncData and fetch), it also means you do not have to expose your API to the public. 
+
+When your site is generated your html is generated with all it's content and on client side navigation these pages are reconstructed using the payload files for your API data. By separating the code from the content you can easily re-generate your content without the need to re-build your whole site. That means once your site is built and you only want to change your content you can simply call `nuxt export` which will re-generate your content only, and as the content doesn't need to go through webpack it means content regeneration is lightening fast. 
+
+If you want to generate static sties, using Nuxt >= v2.13, you will need to add `static` as the `target` in your nuxt.config file. The default value for `target` is `server`.
+
+`nuxt.config.js`
+```js
+export default {
+  target: 'static'
+}
+```
+To learn more about the new static target checkout our [article](/blog/going-full-static)
 
 <div class="Alert">
 
-See [How to deploy on GitHub Pages?](/faq/github-pages) for more details on how to deploy to GitHub Pages.
+See [How to deploy on Netlify?](/faq/netlify-deployment) for more details on how to deploy to Netlify.
 
 </div>

de/guide/modules.md

@@ -303,7 +303,7 @@ module.exports = function () {
 
   // Add hook for generate
   this.nuxt.hook('generate', async (generator) => {
-    // This will be called when a Nuxt generate starts
+    // This will be called when a Nuxt  starts
   })
 }
 ```

de/guide/plugins.md

@@ -149,4 +149,4 @@ Vue.use(VueNotifications)
 
 In case you need to require some libraries only for the server, you can use the `process.server` variable set to `true` when webpack is creating the `server.bundle.js` file.
 
-Also, if you need to know if you are inside a generated app (via `nuxt generate`), you can check `process.static`, set to `true` during generation and after. To know the state when a page is being server-rendered by `nuxt generate` before being saved, you can use `process.static && process.server`.
+Also, if you need to know if you are inside a generated app (via `nuxt export` or `nuxt generate`), you can check `process.static`, set to `true` during generation and after. To know the state when a page is being server-rendered by `nuxt build && nuxt export` or `nuxt generate` before being saved, you can use `process.static && process.server`.