Open greenkeeper[bot] opened 5 years ago
After pinning to 2.4.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
dependency
nuxt was updated from 2.4.3
to 2.4.5
.Your tests are still failing with this version. Compare changes
v2.4.5 (2019-02-26)
asyncData
memory leak on client-side (#4966) (4086800)getNuxtChildComponents
method (#4969) (dbf7099)dependency
nuxt was updated from 2.5.0
to 2.5.1
.Your tests are still failing with this version. Compare changes
dependency
nuxt was updated from 2.5.1
to 2.6.0
.Your tests are passing again with this update. Explicitly upgrade 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_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 2.6.0
to 2.6.1
.Your tests are passing again with this update. Explicitly upgrade to this version π
dependency
nuxt was updated from 2.6.1
to 2.6.2
.Your tests are passing again with this update. Explicitly upgrade 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)dependency
nuxt was updated from 2.6.2
to 2.6.3
.Your tests are passing again with this update. Explicitly upgrade to this version π
dependency
nuxt was updated from 2.6.3
to 2.7.0
.Your tests are passing again with this update. Explicitly upgrade to this version π
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)dependency
nuxt was updated from 2.7.0
to 2.7.1
.Your tests are passing again with this update. Explicitly upgrade to this version π
style
property when resolving (jsless/postcss-import-resolver#2)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.presets
vue-app
utils
serializeFunction
edge casevue-renderer
core
require.resolve
instead of Module
internalsbuilder
nuxtOptions
vue-app
general
auth-jwt
typescript
ci
general
general
dependency
nuxt was updated from 2.8.0
to 2.8.1
.Your tests are passing again with this update. Explicitly upgrade to this version π
vue-renderer
vue-app
console.log
cli
typescript
dependency
nuxt was updated from 2.8.1
to 2.9.0
.Your tests are passing again with this update. Explicitly upgrade to this version π
8.9.0
vue-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 renderAndGetWindow
webpack
build.transpile
vue-app
$nuxt.refresh
app/router.scrollBehavior.js
and deprecate scrollBehavior
<client-only
> alias for <no-ssr>
$nuxt.refresh()
method or refresh the actual page asyncData
and fetch
watchQuery
vue-renderer
typescript
config
devModules
to buildModules
babel-preset-app
babel-plugin-dynamic-import-node
webpack
general
general
babel-preset-app
dependency
nuxt was updated from 2.9.0
to 2.9.1
.Your tests are passing again with this update. Explicitly upgrade to this version π
vue-app
CoffeeScript
additionalExtensions
dependency
nuxt was updated from 2.9.1
to 2.9.2
.Your tests are passing again with this update. Explicitly upgrade to this version π
general
builder
server
https: null
as https: undefined
nuxt-start
vue-client-only
dependencyvue-app
config
core
dependency
nuxt was updated from 2.9.2
to 2.10.0
.Your tests are passing again with this update. Explicitly upgrade to this version π
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.head
config
server.timing
is enabledconfig, vue-app
config
and vue-app
cli, 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
dependency
nuxt was updated from 2.10.0
to 2.10.1
.Your tests are passing again with this update. Explicitly upgrade to this version π
vue-app, webpack
utils
router.trailingSlash
is false
generator
webpack
chunkhash
and contenthash
not work with extractCSS
cli
nuxt build
when pages should be generatedreadme
vue-meta
: Upgraded to v2.3
which fixes duplicated tags in SPA mode
The dependency nuxt was updated from
2.4.2
to2.4.3
.π¨ 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
- β **now:** Deployment has failed ([Details](https://zeit.co/github/deployment?deploymentId=VCIXHORdaHe1jrXLUHQIhTKk)). - β **Travis CI - Branch:** The build **errored**.Release Notes for v2.4.3
terser-webpack-plugin
to^1.2.2
.webpack
to^4.29.2
serializeFunction
for external imports (#4916)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: