Open greenkeeper[bot] opened 5 years ago
dependency
nuxt was updated from 1.4.2
to 2.1.0
.Update to this version instead π
loading.throttle
as an option (PR #3953)undefined
values in vuex store (PR #3913)The new version differs by 27 commits.
d79f9a7
pkg: bump to 2.1.0
fdb225f
2.1.0
d69b4b8
feat: abstract minify and use value for all modes (#3965)
bc90716
fix(deps): update all non-major dependencies (#3991)
0393bf7
feat: use understandable file names for analyze mode (#4014)
8f06a18
feat(builder): allow to customize or disable minimizer plugins (#4018)
1bf6385
fix: wrong extension for dev mode css file
f08cc76
exmaple: remove unnecessary transpile for vuetify
74eb5a6
* Typofixes - https://github.com/vlajos/misspell-fixer (#4013)
0c1d94a
fix(cli): apply default value for NODE_ENV environment variable (#4003)
d7fa66d
meta: improve github templates (#4004)
bb78a92
fix: vue-meta version to 1.5.3
1fef39d
fix(deps): update dependency cssnano to ^4.1.4 (#3990)
163cfab
chore(deps): update all non-major dependencies (#3986)
c097598
chore(deps): update dependency babel-eslint to v10 (#3984)
There are 27 commits in total.
See the full diff
dependency
nuxt was updated from 1.4.2
to 2.2.0
.Update to this version instead π
<nuxt-child/>
accepts keep-alive-props
as props of keep-alive
(PR #4067)The new version differs by 33 commits.
d897890
Merge branch '2.x' of github.com:nuxt/nuxt.js into 2.x
95428c2
version: Bump to v2.2.0
e3b72de
2.2.0
9e0d150
fix(deps): update dependency consola to ^1.4.4 (#4114)
76b10d2
refactor: use more functional programming (#3612)
18802c9
chore: update package.json and yarn.lock
c1028ea
chore(deps): update all non-major dependencies (#4077)
a8875db
chore(deps): update dependency klaw-sync to v6 (#4072)
d35fc8f
fix: warn for non serializable data instead of Error (#4046)
521c377
fix: style module with extractCSS not work well (#4093)
90db0ad
Update theme.js (#4068)
9bb76bc
chore: replace links with speaking equivalents (#4076)
91f319b
chore(deps): update dependency rollup-plugin-commonjs to ^9.2.0 (#4074)
165c80d
fix(SSR plugin): use isJS for matching assets (#3387) (#4073)
963b4dd
chore(deps): update all non-major dependencies (#4069)
There are 33 commits in total.
See the full diff
dependency
nuxt was updated from 1.4.4
to 2.3.0
.dependency
nuxt was updated from 1.4.4
to 2.3.1
.dependency
nuxt was updated from 1.4.4
to 2.3.2
.dependency
nuxt was updated from 1.4.4
to 2.3.3
.Update to this version instead π
The new version differs by 17 commits.
2e90166
update @nuxtjs/opencollective to 0.2.0
f10c982
chore(deps): update dependency vue-meta to ^1.5.6 (#4427)
b7285fe
remove build with devtools tests as feature is not merged yet
b582e70
update patch-only dependencies
289d30f
remove typings
7e1beed
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 mode
ff7c083
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
dependency
nuxt was updated from 1.4.4
to 2.3.4
.Update to this version instead π
(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.2
mini-css-extract-plugin
from 0.4.4
to 0.4.5
webpack
from 4.26.0
to 4.26.1
vue-meta
from v1.5.5
to v1.5.6
opencollective
dependency from nuxt-start
(#4415)lodash
dependency from packages to reduce the nuxt-start
size (#4411)dependency
nuxt was updated from 1.4.5
to 2.4.3
.Update to this version instead π
terser-webpack-plugin
to ^1.2.2
.webpack
to ^4.29.2
serializeFunction
for external imports (#4916)dependency
nuxt was updated from 1.4.5
to 2.4.5
.Update to this version instead π
v2.4.5 (2019-02-26)
asyncData
memory leak on client-side (#4966) (4086800)getNuxtChildComponents
method (#4969) (dbf7099)dependency
nuxt was updated from 1.4.5
to 2.5.1
.Update to this version instead π
dependency
nuxt was updated from 1.4.5
to 2.6.0
.Update to this version instead π
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_modules
yarn 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@2
yarn add -D core-js@2 @babel/runtime-corejs2
npm i -D core-js@2 @babel/runtime-corejs2
core-js@3
yarn add -D core-js@3 @babel/runtime-corejs3
npm i -D core-js@3 @babel/runtime-corejs3
Edit 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
nuxt
bynuxt-edge
, and@nuxt/typescript
by@nuxt/typescript-edge
in the following instructions.
nuxt-ts
dependency (2.4 users only)
yarn remove nuxt-ts
npm remove nuxt-ts
nuxt
and ts-node
to dependencies
:
yarn add nuxt ts-node
npm i nuxt ts-node
@nuxt/typescript
to devDependencies
:
yarn add -D @nuxt/typescript
npm i -D @nuxt/typescript
tsconfig.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)dependency
nuxt was updated from 1.4.5
to 2.6.1
.dependency
nuxt was updated from 1.4.5
to 2.6.2
.dependency
nuxt was updated from 1.4.5
to 2.6.3
.dependency
nuxt was updated from 1.4.5
to 2.7.0
.dependency
nuxt was updated from 1.4.5
to 2.7.1
.dependency
nuxt was updated from 1.4.5
to 2.8.0
.dependency
nuxt was updated from 1.4.5
to 2.8.1
.dependency
nuxt was updated from 1.4.5
to 2.9.0
.dependency
nuxt was updated from 1.4.5
to 2.9.1
.dependency
nuxt was updated from 1.4.5
to 2.9.2
.dependency
nuxt was updated from 1.4.5
to 2.10.0
.dependency
nuxt was updated from 1.4.5
to 2.10.1
.dependency
nuxt was updated from 1.4.5
to 2.10.2
.dependency
nuxt was updated from 1.4.5
to 2.11.0
.dependency
nuxt was updated from 1.4.5
to 2.12.0
.dependency
nuxt was updated from 1.4.5
to 2.12.1
.dependency
nuxt was updated from 1.4.5
to 2.12.2
.
The dependency nuxt was updated from
1.4.2
to2.0.0
.This version is not covered by your current version range.
If you donβt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
Find out more about this release.
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: