Nuxt.js: Update to Vue v2.5.0+

[privatenumber]

Vue 2.5.1 was released last night. Can the dependency in NUXT be updated?

_{This question is available on Nuxt.js community (#c1663)}

[hojas]

And Vue 2.5.2 was released.

[ooade]

Can we just add greenkeeper to keep our packages updated?

[Atinux]

Actually a new version of Vue can bring some breaking changes, that’s why we want to make sure it’s fully compatible before releasing a new version.

Next release coming will have Vue 2.5!

[privatenumber]

@Atinux
Yes, I fully expect thorough testing to come with it.

We were waiting on the "default" feature in provide/inject to be released in 2.5.0+, but currently blocked by NUXT from upgrading; don't mean to rush any work but do you have a ballpark date?

[JamieLottering]

If you can't wait you can manually update all the dependencies using the "resolutions" field.
In your package.json:

"resolutions": {
  "nuxt/vue": "^2.5.2"
}

You'll most likely get a warning that vue has a version mismatch so you'll have to add all of those updated dependencies into the resolutions field until it works. This is also assuming you're using yarn over npm install

[privatenumber]

@JamieLottering Are you sure that's a real property? It's not documented and it didnt work

[JamieLottering]

@hirokiosame That's because it's not an NPM feature, it's a yarn feature

https://yarnpkg.com/en/docs/selective-version-resolutions

[privatenumber]

@JamieLottering Oh sorry I overlooked that. Thank you!

[dohomi]

@Atinux any chance to see rc-12 sometimes soon to make use of the vue 2.5 features? Thanks!

[cliffrowley]

Just FYI if you want to use this now with npm rather than yarn you can simply use the git URL and commit hash.

"dependencies": {
    ...
    "nuxt": "https://github.com/nuxt/nuxt.js#<hash>",
    ...
}

Use this in your dependencies and then npm i and you should be set. As of this writing, the current hash is de2b0a6d5619c5f5334a289ac3287e1ee838b9bc but it'll obviously change as more commits are added.

Note that the commit hash is important because without it you won't get the dev branch.

[privatenumber]

@cliffrowley
Does installing the dev branch work for you? I was under the impression it wouldn't because it doesn't come with distribution files.

[cliffrowley]

Seems to be working just fine for me - are you having issues?

On Sun, 19 Nov 2017 at 15:42 Hiroki Osame [e-mail] wrote:

@cliffrowley https://github.com/cliffrowley
Does installing the dev branch work for you? I was under the impression it
wouldn't because it doesn't come with distribution files.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nuxt/nuxt.js/issues/1851#issuecomment-345526027, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAR5Q30IsG8mZ7YzrZWeJGiZ1beTf62ks5s4Ex5gaJpZM4P486J
.

[pi0]

I can confirm that using GitHub dependency won't work as we need dist files! https://github.com/nuxt/nuxt.js/issues/1851#issuecomment-336948759 is probably this best temporary solution.

[cliffrowley]

shrug I must have been dreaming the past week then...

[pi0]

@cliffrowley I think that's working for you because doing an extra npm install/build inside node_modules/nuxt?

[cliffrowley]

@pi0 nope, I literally just changed my package.json, ran npm i and carried on. I'm using nuxt with express, so maybe that makes a difference? Everything works just fine.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.