リリースノート

v1.0.0-rc4

Improvements

  • New error page by nuxt.js made by @pi0 :)
  • Add file-loader for videos, see PR #1224
  • Upgrade to vue-meta 1.0.5 (fix router transitions with undefined title and kept-alive components)

v1.0.0-rc3

:warning: This is still in heavy development, the API will not change to 1.0 but you may except some bugs.

We are working hard on the documentation, please wait for the new documentation before creating new issues.

We are also working on updating the templates and examples.

Installation

npm install --save nuxt@next

Breaking Changes

  • Aliases are now ~, ~~, @, @@, assets and static (~plugins should be renamed to ~/plugins for example)
  • Programmatic Usage is different now, see custom-server example and updated express template
  • build.loaders has been removed in nuxt.config.js, use build.extend instead
  • injectAs has been removed in plugins, you can inject your plugins by accessing app (see example)
  • process.BROWSER_BUILD has been removed in flavour of process.browser
  • process.SERVER_BUILD has been removed in flavour of process.server
  • Remove ~store and ~router aliases, use plugins to access router and store (see example)

Features / Improvements

nuxt.config.js

  • Add generate.concurrency (default: 500)
  • Add build.devMiddleware to customise webpack-dev-middleware options
  • Add build.hotMiddleware to customise webpack-hot-middleware options
  • Add build.extractCSS option (default to false)

Context

  • nuxtServerInit has now access to context.redirect & context.error
  • context is now given to plugins when they are exporting a function
  • Add context.from (only available on client-side when navigating)
  • Add context.beforeNuxtRender(fn) with async fn({ nuxtState, Components }) (only available on server-side)

v1.0.0-alpha.4

  • Returns empty app when redirected (avoid templates error) (fix #763)
  • Add redirect in plugins context
  • Fix redirect with full URL
  • Modules: this.addPlugin() now unshift the plugins to be executed first

v1.0.0-alpha.3

  • nuxt.build() is now ran automatically on development mode
  • Option build.buildNamespace has been renamed to buildDir
  • JSDOM has been updated to use the latest API (nuxt.renderAndGetWindow)
  • For nuxt generate, you can now give a payload to avoid multiple API call, see this example to see how to use it.
  • context.hotReload (boolean) has been added to know when middleware or page hooks are being called from the hot reload or not (only in development) (fix #812)
  • window.onNuxtReady has been fixed (fix #829)
  • Option dev is now equal to false when process.env.NODE_ENV === 'production'
  • Fix module to be called before listening the server

v1.0.0-alpha2

  • Add index.d.ts for TypeScript compatibility
  • Use webpack-node-externals (PR #780 by @egoist)
  • Optimize generate by giving a payload (PR #768 by @jroxendal)
  • Fix class component TypeEror (PR #765 by @clarkdo)
  • Add build.buildNamespace to manage multiple apps into the same folder (PR #776 by @motia)

v0.10.7

Features

  • Add generate.interval to wait X ms between every render on nuxt generate (@jroxendal via #617)

Improvements

  • Add --config-file option in nuxt dev mode (@alexmoreno via #592)
  • Add chunkNames on Webpack for code-splitted pages and layouts:

screen shot 2017-04-17 at 16 13 57

Bug fixes

  • The bundles are now directly in the dist folder when using nuxt generate with publicPath being an URL (fix #612)
  • Lock version for Vue ~2.2, we are working on implementing Vue 2.3 as soon as possible! (@qm3ster via #637)

v0.10.6

Features

Improvements

  • You now have access to this in the data hook :fire:
  • Give nuxt instance as context (this) to build.extend method (@any35 via #488)
  • Add store parameter in validate method (@agoalofalife via #507)
  • Add babel-preset-es2015 in dependencies to avoid error with some external libraries

v0.10.5

Features

  • Nested Vuex modules are now possible via the file API (@rhwilr via #447), see the vuex-store-modules example
  • Nuxt.js extracts manifest.[hash].jsto bundle the webpack runtime code, improving the vendor bundle cache possibilities (see Webpack doc). The filename is customisable, see build.filenames.manifest.

v0.10.4

Bug fixes

v0.10.3

Features

  • We can now specify the watchers options for chokidar and webpack via nuxt.config.js:
    module.exports = {
    watchers: {
      chokidar: {
        usePolling: true
      },
      webpack: {
        aggregateTimeout: 1000,
        poll: 1000
      }
    }
    }

Improvements

  • Show url after each build #443

v0.10.2

Improvements

  • Watch middleware and store with chokidar to avoid restarting the app when these folders are created during development.

Bug fixes

  • Add store in context before hydrating the client (@evseevn via #442, fix #445)

v0.10.1

Improvements

v0.10.0

✋ Thanks a lot to all the contributors and people helping us to make Nuxt.js better! ✋

This should be the last release with a breaking change before the 1.0! You can see our roadmap here.

Breaking changes

  • data is now asyncData for pages components, it's not asyncData which receives the context and can be asynchronous, this is to respect the vue.js methods. It also fix the mixins with data. If you used the context in your data methods, please rename them to asyncData starting from this release. See updated documentation.
  • Static Generated: generate.routeParams is replaced by generate.routes which has to be an array of dynamics routes called by Nuxt, see updated documentation.

Features

  • Nuxt.js use Vue 2.2.5 and its rendering feature for CSS, no more CSS extracted, only the strict minimum CSS is now included in every page server-rendered!
  • Cache for bundle with hash name are now available, combined with the build.publicPath option, it's a perfect combo for hosting your .nuxt/dist/ files on any CDN!
  • Use the official babel-preset-vue-app for babel default configuration (suggestion by @cj in #271). You can now write JSX directly into your Vue components, see hello-world-jsx example.
  • New option build.publicPath, useful to set CDN url for production deployment or changing the /_nuxt/ path if you don't like it.
  • New option router.mode, let's you define the vue-router mode (default to 'history') (@cj via #272)
  • Add ~middleware alias
  • We can now specify a custom layout for the layouts/error.vue component, see #172
  • The app template is now customisable! Read more on the app.html documentation.
  • nuxt build accept now a -c or --config-file option now (@PierreRambaud via #392)
  • New option: generate.minify to customize html-minifier options.
  • We can now import CSS files directly in <script>, making Nuxt.js compatible with more external libraries.

Improvements

  • nuxt.render now always returns a Promise, even in dev mode when the build is not ready yet
  • Cleaner build/error outputs for terminal (@cj via #274)
  • Nuxt.js prefetch every code-splitted to improve the loading performance when navigating, you have nothing to do, simply upgrade and your app will be faster! (you can disable it via the nuxt.config.js with performance.prefetch: false)
  • We also added gzip support in production (you can disable it via the nuxt.config.js with performance.gzip)
  • store.replaceState(window.__NUXT__.state) is now made before importing the plugin. import store from '~store' in plugins (client-side) will have the store filled.
  • Add duration property in transition

Bug fixes

  • When switching layout, the page component are created only once (fix #214)
  • extendRoutes works with generate + windows paths (fix #275)
  • Middleware are called from error page and the layout is respected when redirected (fix #389)

Examples

v0.9.9

Bug fixes

  • Fix regression from v0.9.8 of routes order (#235)

v0.9.8

Features

  • The middleware feature is out 🔥 ! Read more on the documentation.

You can check the example-auth0 repository to see a real-life example. Otherwise, you can check the i18n example or the middleware example.

  • Wildcard route: _.vue will now create a route { path: '/*', name: 'all' }

Improvements

  • ~store links now to the store file which exports the vuex store instance, useful to require it in plugins to extend it, same for ~router. See documentation.
  • A progress bar is now displayed when building the application (thanks to progress-bar-webpack-plugin)

nuxt-build-progress-bar

  • No need to use a root div for the <nuxt> component (@sirlancelot via #229)

Bug fixes

  • Fix regression from v0.9.7: data was not called anymore when query changed, it's now fixed.
  • Fix bug: routes generated by file names were in the wrong order.

v0.9.7

Features

  • Add the --analyze (or -a) option to nuxt build, this will launch the bundle analyzer to let you see how to improve the size of your bundle. You can also use the build.analyze option, see documentation.
  • It is possible to extend the routes with the extendRoutes property in the nuxt.config.js file, see documentation.
  • You can customise the scrollBehavior of vue-router via nuxt.config.js, see documentation.

Improvements

  • nuxt <command> does not spawn a process anymore, this facilitates the communication between the processes (@yuchonghua via #147)
  • nuxt build and nuxt generate now exit with the status code 1 when the webpack build fail (fix #125)
  • Improve error handling in data and fetch to avoid recursive JSON error (fix #134)
  • nuxt.render sends back a promise to know when the page has been rendered (via #157)

Dependencies

  • Remove cross-spawn dependency
  • Use webpack v2.2.0
  • Upgrade Vue to v2.1.10 and vue-router to v2.1.3

Fixes

  • Fix dynamic page when calling error() and going back to another page (fix #96)
  • The data and fetch methods are not called anymore on hashchange
  • The progress bar works now when switching layout (fix #113)

v0.9.6

Features

  • Add the ability to generate store module with the file API (PR #92), see documentation

Shoutout to @Granipouss for this great feature!

Improvements

  • Use the { isJSON: true } option for serialize-javascript, which improves the performance of server-side rendering and force the component data to be plain object (better security)
  • enterToClass and leaveToClass has been added in the transition options
  • We can now define transition hooks in the nuxt.config.js- #34 (comment)

Patches

  • CSS Modules when building for production (disable extractTextPlugin on the server bundle) (fix #109)
  • Route names for parent routes (fix #119)
  • IE 10 compatibility (fix #93)

Dependencies

  • Upgrade Vue to v2.1.8
  • Upgrade webpack to v2.2.0-rc5, fix #98
  • All dependencies are up to date

v0.9.5

New Features

Using aync/await 🔥

You can use async/await in your components, the best use case is the asynchronous data method.

Example: pages/posts/_id.vue

<template>
  <div>
    <h1>{{ post.title }}</h1>
    <pre>{{ post.body }}</pre>
  </div>
</template>

<script>
import axios from 'axios'

export default {
  async data ({ params }) {
    // We can now use ES7 async/await
    let { data } = await axios.get(`https://jsonplaceholder.typicode.com/posts/${params.id}`)
    return { post: data }
  }
}
</script>

async/await example

See the updated documentation.

Extend webpack configuration

Add extend(webpackConfig, { dev, isClient, isServer }) option in the build configuration. This option let you extend the webpack configuration for your application, this is for advanced users.

Example: nuxt.config.js

module.exports = {
  build: {
    extend (config, { dev, isClient }) {
      // config is the webpack config
      // dev is a boolean, equals false when `nuxt build`
      // isClient is a boolean, let you know when you extend
      // the config for the client bundle or the server bundle
      config.devtool = (dev ? 'eval-source-map' : false)
  }
}

Scroll to the top in page components

Add scrollToTop: true/false option in page component (default: false), this option, when set to true will force the router to scroll to the top of the page (used for children routes).

Core updates

  • The build of Nuxt.js does not use babel-polyfill but directly the required polyfills

Bug fixes

  • Fix the component data on hot-reloading (bug fix) when navigating trough the app

v0.9.4

Bug fixes

  • Fix custom layouts with dash in their names (issue #78), fixed by @pi0 in #79

v0.9.3

🎄 Merry Christmas! 🎄

Custom Layouts

This release should be the last one with breaking a change

Nuxt.js let you now define custom layout for specific page now, to see it in action, please take a look at the our demonstration video.

⚠️ The main breaking changes are:

  • The <nuxt-container> component does not exist anymore (you can simply use a <div> to wrap your layout template)
  • The default application layout is layouts/default.vue instead of layouts/app.vue

🔥 Features:

  • The layout is loaded only when used (webpack code-splitting)
  • You can overwrite the custom layout in layouts/default.vue
  • You can set the which layout to use in the page component with the layout property
  • Define custom head elements depending of the layout

The default layout of Nuxt.js is:

<template>
  <nuxt/>
</template>

Please take a look at the updated documentation.

Bug fixes

Tests

More tests has been added to cover the bug fixes and also the layout feature.

Dependencies

  • Upgrade autoprefixer to v6.6.0
  • Upgrade debug to v2.5.1
  • Upgrade lodash to v4.17.3
  • Upgrade vue to v2.1.7
  • Upgrade webpack to v2.2.0-rc.2
  • Upgrade webpack-hot-middleware to v2.14.0

v0.9.2

Features

  • When a dynamic route is created in a folder without index.vue, the parameter will be optional:
pages/
--| users/
-----| _id.vue

Will create the route /users/:id?.

Improvements

  • nuxt.renderAndGetWindow(url) does not need jsdom as the first argument anymore, it will try to require it automatically (renderAndGetWindow is made to faciliate the tests with Nuxt.js)
  • Nuxt.js has now 100% of coverage

Bug fixes

  • Fix nuxt generate minified HTML which was not working because of the removeComments: true option
  • Fix nuxt generate on validate({ query, params }) method -> not server-render it when not valid
  • Fix crash when children has no data method
  • Fix validate() call on children routes

v0.9.1

Improvements

  • Upgrade dependencies (Vuex 2.1.1 & Vue 2.1.6)
  • Set preserveWhitespace: false in vue-loader configuration to avoid SSR mismatch error
  • Improve the call to data() when staying in the same view but the query changed

v0.9.0

Breaking Changes

The 0.9.0 is an important release, we can now define dynamic routes without the nuxt.config.js file, please read more in examples/custom-routes/

The router.routes object does not exist anymore, this gives a better readability for any Nuxt.js project without removing any features.

We also introduce a validate({ params, query }) method to validate the routes params/query before entering the the data method, if you return false, the error page will be displayed with a 404.

Also, we can now define children routes by creating a directory with the same name as the file, example:

-| pages/
---| parent/
-----| child.vue
---| parent.vue

And then, in your parent.vue component, you can add <nuxt-child></nuxt-child> to display the child component (when navigating to /parent/child)

Features

  • JavaScripts hooks can be defined in the transition property. To see the list of props and events: https://vuejs.org/v2/api/#transition transition can also be a function (to, from) { return 'fade' } so you can set a different transition depending of the route destination
  • Introduction <nuxt-link> which is exactly the same as <router-link> but in the future, will add lazy-loading and more 🔥

If you were using the class .router-link-active, please replace it to .nuxt-link-active, or if you want to keep the router-link-active class, update your nuxt.config.js like this:

module.exports = {
  router: {
    linkActiveClass: 'router-link-active'
  }
}

Improvements

  • You can import components without giving the .vue extension now (fixed #59)
  • In development mode, when the nuxt.config.js file changed with a syntax error, the server will not crash (fixed #60)
  • Upgrade to webpack 2.2.0-rc.0
  • build.babel options are given to the vue-loader as well. Now you can write JSX in your vue components, see https://gomix.com/#!/project/nuxt-hello-world-jsx

Bug fixes

  • Fix importing .js file with ES6 syntax in .vue files (Fix #63)
  • Use cross-env for setting NODE_ENV=production on Windows (#65)
  • Avoid the renderer error when nuxt.config.js change on nuxt (#66)

What's next?

Before launching the 1.0.0, we are working on:

  • 100% coverage with a lot of tests because it's really important for us to deliver a reliable framework
  • The ability to add middleware to your routes, useful for having routes that need the user to be authenticated first
  • config.build.publicPath, see #25
  • nuxt.renderStream and nuxt.renderRouteStream, see #26
  • Generate filenames with chunkName for avoid CDN caching
  • A complete documentation on nuxtjs.org
  • Real-life examples
  • Improvements and bug fixes

v0.8.8

Improvements

  • Nuxt.js is now compatible with node 4 and higher (Using babel and webpack)
  • Add test and coverage (ava, jsdom and nyc)

v0.8.6

Bug fixes

  • Fix error.vue layout path with srcDir (#54)

v0.8.5

Fix

  • Push the srcDir feature to npm (fix #53)

v0.8.4

Features

  • Add srcDir option allowing you to have your pages directory and other source folder for Nuxt.js in a sub directory, see #44 for more details (credits to @cj)

Improvements

  • Optimise generate() when generating +100,000 paths, calling them 500 by 500 to avoid out of memory

v0.8.3

Bug fixes

  • Fix layouts/error.vue which was not assigned to the right variable when existing

v0.8.2

Bug fix

  • Set window.onNuxtReady before importing the plugins so we can use this hook inside them