greenkeeper[bot]
commented
5 years ago - The
dependencynuxt was updated from2.3.0to2.3.1.
Your tests are still failing with this version. Compare changes
Open greenkeeper[bot] opened 5 years ago
greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.3.0 to 2.3.1.Your tests are still failing with this version. Compare changes
greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.3.1 to 2.3.2.Your tests are still failing with this version. Compare changes
greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.3.2 to 2.3.3.Your tests are still failing with this version. Compare changes
The new version differs by 17 commits.
2e90166 update @nuxtjs/opencollective to 0.2.0f10c982 chore(deps): update dependency vue-meta to ^1.5.6 (#4427)b7285fe remove build with devtools tests as feature is not merged yetb582e70 update patch-only dependencies289d30f remove typings7e1beed perf(pkg): remove lodash dependency from packages (#4411)4a85c03 fix(pkg): move opencollective dependency nuxt and nuxt-legacy (#4415)d187793 fix(server, vue-app): allow unicode page names (#4402)e1c1240 fix(server, jsdom): fix timeout error message (#4412)0c6c69b fix(scrollBehavior): emit triggerScroll event after changing layer (#4399)8030ca1 fix(progress-bar): allow 0 for values and remove duplicate defaults (#4397)54d2737 fix: router Expected "0" to be defined (#4394)47f02ae fix: empty error message in dev modeff7c083 fix: modern=true or false not work as expected (#4378)b12141b hotfix: nuxt-start tries to build instead of starting (#4384)There are 17 commits in total.
See the full diff
greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.3.3 to 2.3.4.Your tests are still failing with this version. Compare changes
(Please skip v2.3.3 release. It was mistaken.)
nuxt-start command should always start nuxt in production mode (#4384)modern=true or false didn't work as expected (#4378)triggerScroll event after changing the layout (#4399)0 values for progress bar attributes (#4397)vue-router from 3.0.1 to 3.0.2 (#4394)@nuxt/friendly-errors-webpack-plugin from 2.3.0 to 2.3.2mini-css-extract-plugin from 0.4.4 to 0.4.5webpack from 4.26.0 to 4.26.1vue-meta from v1.5.5 to v1.5.6opencollective dependency from nuxt-start (#4415)lodash dependency from packages to reduce the nuxt-start size (#4411)greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.3.4 to 2.4.0.Your tests are still failing with this version. Compare changes
We are really proud to announce Kevin Marrec (@kevinmarrec) as a new core team member of Nuxt.js. He is French
We now offer official support & consulting from the core team. We partnered with Otechie for the process and already did some beta-tests with selected companies.
Are you interested or curious?
Learn more on https://otechie.com/nuxt
We invite you to take a look at our nuxt/rfcs repository where we discuss the future of Nuxt and its vision.
Here are some interesting proposals if you want to learn more about the upcoming changes of Nuxt:
config/ directory and autocompleteStarting with this release, Nuxt will adhere to a formalized release plan (as good as possible). Also, an end of life for older major versions is defined within RELEASE_PLAN.md.
Quick summary:
We strongly invite you to read the RELEASE_PLAN.md for further details.
We want to specially thanks:
TypeScript support has landed!
In order to run Nuxt with TypeScript, we created a new distribution, called nuxt-ts (we also have nuxt-ts-edge).
We want to thank @hmsk for his donation of the package name on npm
You can explore Nuxt TypeScript example or play with it directly in our Nuxt TS CodeSandBox.
For a more advanced example, you can look at the HackerNews-TS repo or play with it on CodeSandBox, made by @husayt & @kevinmarrec.
This work has been made by @kevinmarrec with the help of @pi0 & @Atinux.
Nuxt.js will automagically prefetch the code-splitted pages linked with <nuxt-link> when visible in the viewport by default. This hugely improves the end user performances, inspired by quicklink.
Demos are online and we recommend you to try it out to feel the difference:
Bonus: we added $nuxt.isOnline and $nuxt.isOffline which is reactive, so you can use it directly inside your components (see this example).
You can learn more about this feature in the associated PR #4574 and in the documentation.
store/ Save more development time with full HMR support for the store (
mutations,getters, andactions).
This feature has been implemented by @manniL & @Atinux on PRs #4589, #4582 and #4791
If you are using VS Code, with this version, you will now have autocomplete for Nuxt.js components:
This feature has been implemented by @octref & @Atinux on PR #4524
If Nuxt wants to listen on a port which is already used, it will warn you in development and listen to a free port instead:
In production it will throw an error instead to avoid unwanted behavior:
This feature has been implemented by @ricardogobbosouza on PR #4428 with the help of @pi0 and @manniL.
Nuxt requires all peer like dependencies as a dependency for easier usage. Sometimes this causes unwanted behaviors when users explicitly add a specific version in their package.json which is incompatible with nuxt. This could also help to resolve popular Vue packages version mismatch error (#198, #669, #1084, #1414, #1851, #2079, #2406, #3454).
Nuxt is now able to automatically self-verify installed dependencies and warn with a proper message in case of detecting problems.
This feature has been implemented by @pi0 in PR #4669
When running nuxt start, Nuxt will automatically detect if you built your app modern mode enabled. No need to run nuxt start --modernexplicitly anymore
This detection was created by @clarkdo on PR #4422
Until now, you used ssr: false in your plugin declarations to disable server-side rendering. We decided to deprecate that option and introduce a mode instead, which can be 'all', 'client' or 'server'. No worries, ssr is still working (until Nuxt 3).
The new feature coming with the mode is that you can define it by using the file suffix:
plugins/plugin.server.jsplugins/plugin.client.jsplugins/plugin.jsBy adding the plugins to your nuxt.config.js:
plugins: [
'~/plugins/plugin.server.js',
'~/plugins/plugin.client.js',
'~/plugins/plugin.js'
]The declaration will be internally transformed to:
plugins: [
{ mode: 'server', src: '~/plugins/plugin.server.js' },
{ mode: 'client', src: '~/plugins/plugin.client.js' },
{ mode: 'all', src: '~/plugins/plugin.js' }
](If you specify the mode manually, it will overwrite the suffix detection)
This feature has been implemented by @clarkdo on PR #4592
Nuxt modules can now include bin scripts that are recognized by Nuxt's CLI.
Here's an example of my-module/bin/command.js:
#!/usr/bin/env node
const consola = require('consola')
const { NuxtCommand } = require('@nuxt/cli')
NuxtCommand.run({
name: 'command',
description: 'My Module Command',
usage: 'command <foobar>',
options: {
foobar: {
alias: 'fb',
type: 'string',
description: 'Simple test string'
}
},
run(cmd) {
consola.info(cmd.argv)
}
})The command could be run with:
npx nuxt command arg1 arg2You can learn more about that in the modules command documentation.
This feature has been implemented by @galvez on PR #4314 with the help of @pi0.
You can now use lang="postcss" in your Vue components. Postcss has applied to all your styles anyway (e.g. to resolve aliases like ~) but the lang attribute enables autocomplete and syntax highlighting for some IDEs.
This feature has been implemented by @manniL on PR #4417.
We are concerned to improve the Developer Experience ("DX") with each release. This small change allows you to omit the file extension for CSS/SCSS/Postcss/Less/Stylus/... files listed in the css array inside your nuxt.config.js. For the plugins or serverMiddleware key, this is already possible.
This feature has been implemented by @manniL on PR #4671.
We made a full rewrite of how SSR bundle is packaged.
This means better performance, less memory overhead, fewer OOM crashes and easier SSR bundle debugging.
| _ | Before | After | Diff |
|---|---|---|---|
| Dist | 8.2M | 7.2M | -1M / 12% |
| Dev | 281 MB (RSS: 439 MB) | 237 MB (RSS: 354 MB) | -44M / 16% (RSS: -85M / 19%) |
| Start | 106 MB (RSS: 169 MB) | 71.7 MB (RSS: 137 MB) | -34M / 32% (RSS: -32M / 19%) |
This feature has been implemented by @pi0 on PR #4439.
process.modern can be used for distinguishing modern environment.server.timing to give Server-Timing header, useful for monitoring and performances overview (PR #4800)HardSourceWebpackPlugin by hardSource: true in hardSource of nuxt.config.jsscrollToTop to false in pages (PR #4564)nuxt-link and nuxt-child (n-link and n-child) are available now (PR #4525)PascalCase as recommended by the Vue styleguide (PR #4396)headAttrs are now supported for the appTemplate (PR #4536)crossorigin attribute (PR #4472)compression middleware (PR #4381)FriendlyErrorsWebpackPlugin overlay (PR #4381)exclude option to exclude pages from being generated (in static mode) but still get rendered via fallback/SPA (PR #4754)build.hotMiddleware.client (PR #4796)middleware correctly when using Vue.extend in layout (fix #4724)undefined script in modern mode & generated (0a21d4b)publicPath is falsy (PR #4365)$nuxt.$loading typedefs (#4778)loading property to Component options (#4786)greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.4.0 to 2.4.1.Your tests for group default are passing again with this update. Explicitly upgrade default to this version π
greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.4.1 to 2.4.2.Your tests for group default are passing again with this update. Explicitly upgrade default to this version π
greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.4.2 to 2.4.3.Your tests for group default are passing again with this update. Explicitly upgrade default to this version π
terser-webpack-plugin to ^1.2.2.webpack to ^4.29.2serializeFunction for external imports (#4916)greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.4.3 to 2.4.5.Your tests for group default are passing again with this update. Explicitly upgrade default to this version π
v2.4.5 (2019-02-26)
asyncData memory leak on client-side (#4966) (4086800)getNuxtChildComponents method (#4969) (dbf7099)greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.5.0 to 2.5.1.Your tests for group default are passing again with this update. Explicitly upgrade default to this version π
greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.5.1 to 2.6.0.Your tests for group default are passing again with this update. Explicitly upgrade default to this version π
This version is addressing most of the problems of 2.5 and is without any breaking changes. For most of the users, a normal version upgrade would be enough. However, reading this guide can help to have a smooth upgrade.
yarn.lock, package-lock.json and node_modulesyarn outdated command can be used.Because of how package managers (yarn, npm) work, a wrong version of a dependency from one of the other dependencies may be hoisted into node_modules. Nuxt is strict about this and provides instructions for dependency resolution so please follow it.
The well-known problem is with firebase package that requires to manually install node-fetch dependency in your project.
Since core-js@2 and core-js@3 are both supported from babel 7.4.0, Starting from 2.6 Nuxt supports both versions (#5411). It is highly advised to stick with 2 (default) unless having a special dependency that needs 3. (Instructions for core-js@2 are not required but recommended)
core-js@2yarn add -D core-js@2 @babel/runtime-corejs2npm i -D core-js@2 @babel/runtime-corejs2core-js@3yarn add -D core-js@3 @babel/runtime-corejs3npm i -D core-js@3 @babel/runtime-corejs3Edit nuxt.config.js:
export default {
build: {
babel: {
presets({ isServer }) {
return [
[
require.resolve('@nuxt/babel-preset-app'),
// require.resolve('@nuxt/babel-preset-app-edge'), // For nuxt-edge users
{
targets: isServer ? { node: '10' } : { ie: '11' },
corejs: { version: 3 }
}
]
]
}
}
}
}Nuxt 2.5 users may only require to add ts-node to the dependencies
Beta Testers : Replace
nuxtbynuxt-edge, and@nuxt/typescriptby@nuxt/typescript-edgein the following instructions.
nuxt-ts dependency (2.4 users only)
yarn remove nuxt-tsnpm remove nuxt-tsnuxt and ts-node to dependencies:
yarn add nuxt ts-nodenpm i nuxt ts-node@nuxt/typescript to devDependencies:
yarn add -D @nuxt/typescriptnpm i -D @nuxt/typescripttsconfig.json file. Nuxt will automatically generate it with defaults at first run, then you can edit it to fit your needs--quiet option to nuxt generate command (#5357) (Franck Abgrall) (91f4eb0)tsconfig.json (#5412) (Pooya Parsa) (6ffc5c5)babel.config.js by default (#5365) (Xin Du (Clark)) (64fa424)getlocation (#5337) (Johan Roxendal) (77dcfe6)unsafe-inline hasn't been specified (#5387) (Sam Bowler) (97db6a4)greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.6.0 to 2.6.1.Your tests for group default are passing again with this update. Explicitly upgrade default to this version π
greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.6.1 to 2.6.2.Your tests for group default are passing again with this update. Explicitly upgrade default to this version π
nuxt.config.js changes and watch for all imported files (#5500)tsconfig.json but do not use typescript (#5478)nuxt dev (#5514)modulepreload for modern mode when using spa generate (#5489)@nuxtjs/style-resources package (#5499)router.base support for banner url and loading screen (#5470) (nuxt/loading-screen#8)vuex-router-sync (nuxt/devalue#8) (vuejs/vuex-router-sync#89)greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.6.2 to 2.6.3.Your tests for group default are passing again with this update. Explicitly upgrade default to this version π
greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.6.3 to 2.7.0.Your tests are still failing with this version. Compare changes
We all know the console.log debugging method, but when working with universal applications, you have to remember that sometimes, your logs are in your terminal and not in your browser console.
This can be really annoying when developing a Nuxt.js application, starting with this version and running nuxt dev, the ssr logs are now reported to your browser console:
store/ creation Nuxt.js now detects when you created a store/ directory and will reload himself auto-magically so you don't have to restart it anymore.
PS: We also improved the serverMiddleware watch to restart Nuxt.js and clean their cache
watch:restart after watch:fileChanged hook (#5620)watchQuery option in routerViewKey (#5516)spa:templateParams hook (#5619)HardSourcePlugin (#5653)serverMiddleware paths (#5681)transition to pageTransition and deprecate it (#5558)babel.presets and babel envName (#5637)core-js@3 example in the readme (#5633)Only for typescript users, Nuxt.js v2.7 dropped support for node < 8.6 relate to ts-loader v6
context.app type (#5701)extendRoutes method type (#5700)ts-node to register twice (#5699)greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.7.0 to 2.7.1.Your tests for group default are passing again with this update. Explicitly upgrade default to this version π
style property when resolving (jsless/postcss-import-resolver#2)greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.7.1 to 2.8.0.Your tests are still failing with this version. Compare changes
pages/ creation when default page displayedvue-renderer
server
builder
generator
types
babel.presetsvue-app
utils
serializeFunction edge casevue-renderer
core
require.resolve instead of Module internalsbuilder
nuxtOptionsvue-app
general
auth-jwt
typescript
ci
general
general
greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.8.0 to 2.8.1.Your tests for group default are passing again with this update. Explicitly upgrade default to this version π
vue-renderer
vue-app
console.logcli
typescript
greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.8.1 to 2.9.0.Your tests for group default are passing again with this update. Explicitly upgrade default to this version π
8.9.0vue-meta upgraded to 2.0.0. Please refer to the changelog to review notable changes.scrollBehavior option is deprecated in favor of app/router.scrollBehavior.js (#6055)devModules option is deprecated in favor of buildModules (#6203)general
renderer
nomodule scripts in safari 10cli
nuxt & nuxt-edge being installedvue-app
vue-renderer
webpack
cli
server
loadingTimeout and other arguments to renderAndGetWindowwebpack
build.transpilevue-app
$nuxt.refreshapp/router.scrollBehavior.js and deprecate scrollBehavior<client-only> alias for <no-ssr>$nuxt.refresh() method or refresh the actual page asyncData and fetchwatchQueryvue-renderer
typescript
config
devModules to buildModulesbabel-preset-app
babel-plugin-dynamic-import-nodewebpack
general
general
babel-preset-app
greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.9.0 to 2.9.1.Your tests for group default are passing again with this update. Explicitly upgrade default to this version π
vue-app
CoffeeScript
additionalExtensionsgreenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.9.1 to 2.9.2.Your tests for group default are passing again with this update. Explicitly upgrade default to this version π
general
builder
server
https: null as https: undefinednuxt-start
vue-client-only dependencyvue-app
config
core
greenkeeper[bot]
commented
4 years ago dependency nuxt was updated from 2.9.2 to 2.10.0.Your tests are still failing with this version. Compare changes
loading-screen. No more endless loops (nuxt/loading-screen#44) and show fatal errors (nuxt/loading-screen#45) for the initial buildcore
vue-app
webpack
cli
babel-preset-app
vue-renderer
options.headconfig
server.timing is enabledconfig, vue-app
config and vue-appcli, config
cli.bannerColor optionconfig
serverMiddleware as a simple key/value objectbuilder
cli
cli:buildError hookwebpack
server
etag hash functionvue-app
general
vue-meta options by userutils
builder, router
cli
builder
build.createRoutes to allow async functions inside itbabel-preset-app
with-sockets
general
greenkeeper[bot]
commented
4 years ago dependency nuxt was updated from 2.10.0 to 2.10.1.Your tests are still failing with this version. Compare changes
vue-app, webpack
utils
router.trailingSlash is falsegenerator
webpack
chunkhash and contenthash not work with extractCSScli
nuxt build when pages should be generatedreadme
vue-meta: Upgraded to v2.3 which fixes duplicated tags in SPA modegreenkeeper[bot]
commented
4 years ago dependency nuxt was updated from 2.10.2 to 2.11.0.Your tests are still failing with this version. Compare changes
utils
vue-app
general
webpack
config
unsafeInlineCompatibility namevue-app
vue-router to 3.1.xgeneral
vue-renderer
config
ignoreOptions for node-ignoreserver
webpack
contenthashwith-sockets
general
docs
ci
github
general
greenkeeper[bot]
commented
4 years ago dependency nuxt was updated from 2.11.0 to 2.12.0.Your tests are still failing with this version. Compare changes
general
wepack
vue-app
cli
nuxt.config exports a functionbuilder
general
generator
cli
vue-app
core
vue-renderer
core
render:context and render:routeContext hooks was not being calledbabel-preset-app
vue-app
webpack
URL and URLSearchParamsgeneral
utils
cached-components
general
greenkeeper[bot]
commented
4 years ago dependency nuxt was updated from 2.12.0 to 2.12.1.Your tests for group default are passing again with this update. Explicitly upgrade default to this version π
vue-app
builder
readme
examples
postcss.config.jsgreenkeeper[bot]
commented
4 years ago dependency nuxt was updated from 2.12.1 to 2.12.2.Your tests for group default are passing again with this update. Explicitly upgrade default to this version π
The dependency nuxt was updated from
2.2.0to2.3.0.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
nuxt is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
- β **ci/circleci: test:** Your tests failed on CircleCI ([Details](https://circleci.com/gh/likecoin/likecoin-button/423?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)).FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donβt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: