Closed greenkeeper[bot] closed 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.
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_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 still failing with this version. Compare changes
The dependency nuxt was updated from
2.5.0
to2.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 failed ([Details](https://travis-ci.org/mazipan/quran-offline/builds/509656854?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: