greenkeeper[bot]
commented
5 years ago After pinning to 2.5.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Closed greenkeeper[bot] closed 4 years ago
greenkeeper[bot]
commented
5 years ago After pinning to 2.5.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.5.1 to 2.6.0.Your tests are still failing with this version. Compare changes
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 are still failing with this version. Compare changes
greenkeeper[bot]
commented
5 years ago dependency nuxt was updated from 2.6.1 to 2.6.2.Your tests are still failing with this version. Compare changes
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 are still failing with this version. Compare changes
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 are still failing with this version. Compare changes
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 are still failing with this version. Compare changes
vue-renderer
vue-app
console.logcli
typescript
greenkeeper[bot]
commented
5 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
5 years ago dependency nuxt was updated from 2.10.1 to 2.10.2.Your tests are still failing with this version. Compare changes
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
The dependency nuxt was updated from
2.5.0to2.5.1.π¨ 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
- β **continuous-integration/travis-ci/push:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/TheNoim/fastify-vue/builds/509657192?utm_source=github_status&utm_medium=notification)).Release Notes for v2.5.1
Bug Fixes
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: