v3.0.0-rc.14

[pi0]

Note
This is the last release candidate for Nuxt v3! Are you ready? 👀

⚠️ Breaking Changes

• cli: Setup nuxt globally with nuxt test (#4578)
• nuxt: Only add $f fetch prefix to auto-keys (#8852)
• test-utils: Use vitest/node subpath export (#8815)
• nuxt: Remove initialCache option (#8885)
• nuxt: Enable payload extraction only for nuxi generate (#9018)
• nuxt: Include request url and params in useFetch key (#6632)
• nuxt: Fix typo for NuxtRenderHTMLContext.bodyPrepend (#8712) (#8704)
• nuxt: Remove support for 404.vue shorthand (#8809)
• kit: Remove support for module container (#9010)
• nuxt: Move head option support into defineNuxtComponent (#8901)
• Remove deprecated api (#9029)

compare changes

👉 Full Changelog

[Vi-jay]

Isn't the official version released today?

[kissu]

What do you mean? Nuxt getting out of RC and being 100% stable? 🎊
It is still planned indeed. 😉

Most VueJS' big announcements have (tested) "last minute" pushes so that it creates the surprise.
You even have commits 2 minutes before a conference's start sometimes. 😂
But usually, those kind of releases are totally fine! 🎩

[gcentervn]

(*) Edge releases are automated after each commit passing tests
Read here: https://v3.nuxtjs.org/community/roadmap#current-releases

[kissu]

I speak on behalf of the community in thanking the team for their huge daily deliveries. 😻
The amount of fixes + improvements in the last weeks/months was relentless and achieved with the collaboration of everybody here!
Thank you for giving of yourself as humans in every possible way! 🙏🏻

See you all in a few hours at NuxtNation for the actual official announcements. 🎊

[alvarosabu]

@Maxp777 I'm sorry you feel like that tho, though maybe take a look at the commits involved in the Nuxt3 development, to see if validates your impression.

About the error, have you checked if there is an open ticket already? If not you mind creating one with a reproducible so we can help you?

[kissu]

@Maxp777 people speaking at conferences and the ones making the project move forward code-wise are not always the same.
When they are, it's actually quite beneficial because it also provides some feedback for the core team, so that the final product can be improved. 💪🏻
OSS is not only coding or promoting, it's also a lot of things in-between or mixed-up.

As a public speaker myself I can attest that this is necessary and actually...it doesn't take that much of your time (to prepare a talk) if you're doing something daily.
But don't think that Sébastien Chopin or Daniel Roe are spending their time creating fancy slides haha.

[BayBreezy]

Give it some time.. the team has been working real hard.
This is just the start of something great.. Nuxt v2 was not great when it was just released either but it matured into something beautiful. Nuxt v3 will follow the same path(all new tech stuff follow this path) its never perfect the first time but it does get better.

[kissu]

Not sure where you're getting your stats from, but NPM does not agree with you at all.
On top of that, NPM download/such stats are quite naive overall and need to be taken into account sparingly.
There are quite a few reasons for such, won't get into details here about Vue2/Vue3 differences (already wrote some leads in the comments of my answer) but you cannot make a direct comparison.

Not count of commits imports.

Not sure what you mean by that one.

All people find other solutions while waiting for nuxt 3.

The given solutions may be Vitesse, Astro or even vite-plugin-ssr?
2 of those are tied pretty closely to our core team maintainers tbh. 😄
Or maybe you're thinking about Laravel/else even? You can give Nuxt a try as of right now, may be totally fine for your use case. 😉

If you have any frustration, there are people to help you. 💚
They are here daily and only require a few minutes of your time (mainly a repro) to get everybody started on the same page.
You don't need to be angry at them, but at JS' pace at best.

If things break, it's because they are moving fast.
Daniel Roe/Pooya/[...rest of our contributors] are not breaking the currently working code just for fun. They are trying to move at the same pace + add features at the same time.

No one will use some product because on TV people say that it is great. They will buy it once, will see that it is bad. And will drop it to trash.

I dare you to name me a single JS project that worked flawlessly out of the box in it's first iteration.
Please name at least one project that:

• caused 0 frustration
• got close to no breaking change
• still bringing something quite new and deal breaker to the table

I can't think about any of them even tho I've starred almost 1000 projects as of today.

Now, regarding the 📺 part. I don't feel like a conference is a TV or at least, a close medium in any way.
You are not forced to listen to it, you are not forced to agree to it. You can join the event and get hyped tho!

It's literally like hanging with some friends around something that the whole group enjoys. 🍻
But keep in mind that it doesn't block anything regarding the pacing of the code delivery. You will not have 3 months allocated for a presentation and the speakers of the Nuxt team will not give prio to a conference over some critical piece of code delivery.

Meanwhile, you need to also promote your thing.
Nuxt is free. You're not paying anything and the team does not sell you any kind of freemium.
You can even fork it and do whatever you want with it. How cool is that? 🎊
Keep in mind that it's founder 101 here: you need to share the word around, let people know that things are moving so that they can be included into the discussion, contribute to a feedback loop, get their issues/wishlist considered and so much more.

Basically: Community. 🤗
All what Nuxt or any OSS is about, pretty much.
The core team is not selling a razor blade nor a VPN all over the place on TV, newspaper etc...but on a small platform with a few developers stocked for the latest goodies! 🍬

I think the team of people that know how to make nuxt is need to be bigger, to do things better.

Perfect transition. How do you grow a team?
By hiring more people. How do you feed them at the end of the month?
With money. How do you still make money as an OSS (Nuxt is free, as a reminder)?
By making your product nice and getting some investors to believe into your thing (startup fundraising pretty much).
Which is...pretty much one aspect as of why you get the conference in the first place.
So that people can see some progress. Get some money from investors. Feed their family. Grow together.

Does it sound fair viewed from that aspect? Do you see it as a "marketing" thing still?

You can put thumbs down, but that not change situation, the impression from nuxt, it's magic disappeared.

I did not downvoted you, I respect your opinion.
As for the magic, as with everything in life: things tend to become boring/less exciting.
This is not a Nuxt thing, just how our human brain works: you get used to things.
It requires some work and some hype to move forward all together.

May be because I previously not work with beta versions.
And in generally that all troubles with javascript and Node.js

That one could explain a lot indeed. 💯
Welcome to the less exciting part of shipping a heavy update on a big product! 🚄

---

To finish, if you want to get some positive vibes from the community.
This is an excellent place to fill yourself with positive energy and give Nuxt3 another try. 🙏🏻
We're here to help you out in case something goes wrong. 💪🏻

[Vivi-Ornitier]

When I run nuxi build with rc.14, I get the following error.

 ERROR  Cannot read properties of undefined (reading 'options')                                                                                                            14:07:39

  at nuxtModule (node_modules/@nuxtjs/eslint-module/dist/module.js:25:13)
  at installModule (node_modules/nuxt/node_modules/@nuxt/kit/dist/index.mjs:416:9)
  at async initNuxt (node_modules/nuxt/dist/index.mjs:1827:7)
  at async loadNuxt (node_modules/nuxt/dist/index.mjs:1859:5)
  at async loadNuxt (node_modules/@nuxt/kit/dist/index.mjs:732:19)
  at async Object.invoke (node_modules/nuxi/dist/chunks/build.mjs:34:18)
  at async _main (node_modules/nuxi/dist/cli.mjs:50:20)

Do you know the reason?

[kissu]

Latest LTS for Node is 18.12.1, mind giving that one at try? 😄

[BenjaminOddou]

Maybe this can be link to the deprecated options removed in this rc14 version ? See this PR

[Vivi-Ornitier]

It was caused by using @nuxtjs/eslint-module.
Thank you for answering.

[r-modica-cti]

@Vivi-Ornitier what did you do to resolve the issue? we are having the same one.

[alex-arabadjiev]

We are having the same issue with @nuxt/typescript-build. @Vivi-Ornitier could you tell us what you did to solve this issue?

[RajendraUppu]

i just updated my project from rc-12 to rc-14 i'm getting this weird error on v-model="modelValue" even tough im emitting the modelValue... but in rc-12 it's working perfectly without any errors or warning.

it's appearing on codemirror component, from vue-codemirror library which supports two-way binding using modelValue.

[plugin:vite:vue] v-model cannot be used on a prop, because local prop bindings are not writable.
Use a v-bind binding combined with a v-on listener that emits update:x event instead.

[RajendraUppu]

Sure, ill update the repo link..

[RajendraUppu]

@kissu here you go: repo Link - https://stackblitz.com/edit/nuxt-starter-jobax1?file=app.vue

[RajendraUppu]

@kissu

[makhweeb]

@kissu

[Corey-Evans]

@kissu Hi, this is still happening in the stable release. Can we please have some clarification if this is expected behaviour going forward or if it is a bug. Cheers

[oktapascal]

i just updated from rc 13 to rc 14. but i got error like this in nuxt.config, how to fix it?

[sadeghbarati]

buildModules is deprecated in nuxt3 use nuxt.config.ts (TypeScript) instead

use modules

[oktapascal]

Thanks for the advice

[iyashpal]

Can anyone help me to resolve this?

[ExEr7um]

Well yes, it's an issue with @nuxt/image-edge. Made a reproduction: https://stackblitz.com/edit/nuxt-starter-idfvjn.

[wallchr]

Removing @nuxt/image-edge fixed the issue for me.

[iyashpal]

removing @nuxt/image-edge fixed the issue for me too.

[sadeghbarati]

nuxt/image#648

https://github.com/nuxt/image/blob/4b27db34afc3e3e9aa58ca64275d245b6aa2fa79/src/module.ts#L2

[codelegant]

@pinia/[email protected] has solved this problem.

[dodanex]

Any ideas about this error?
I have searched for useMeta inside my project and I can't find anything.

[harlan-zw]

vueuse/vueuse#2449

Nice catch! Will try get that pushed through

[sadeghbarati]

@harlan-zw

since vueuse/motion use latest @nuxt/kit": "npm:@nuxt/kit-edge@latest that might caused error too

https://github.com/vueuse/motion/blob/main/src/nuxt/module.ts

---

addAutoImport => addImports

• vueuse/motion
• nuxt-modules/algolia
• github-module
• design-tokens

[pi0]

/cc @Tahul @farnabaz

[dodanex]

I think I found the issue: The problem was with vueuse config.

I had this inside nuxt.config.ts:

vueuse: {
	ssrHandlers: true
}

Then after I commented // ssrHandlers: true it's working!
Thank you all!

[mittci]

Rename useMeta to useHead https://github.com/nuxt/framework/issues/4062

Is need to replace useMeta with import { useHead } from '#imports' ?!

[Vivi-Ornitier]

Removed initialCache option from useFetch?
TS2345 error started from rc.14.

[BayBreezy]

Removed initialCache option from useFetch? TS2345 error started from rc.14.

Yup.. That was removed

[Vivi-Ornitier]

Are there alternative options?

[manniL]

Nope. nuxt/framework#8885

[abdonrd]

After update from 3.0.0-rc.13 to 3.0.0-rc.14, we have this error:

vue-router.mjs:3451 Error: [🍍]: getActivePinia was called with no active Pinia. Did you forget to install pinia?
	const pinia = createPinia()
	app.use(pinia)
This will fail in production.
    at useStore (pinia.mjs:1696:19)
    at auth.ts:9:3
    at fn (nuxt.mjs?v=184e88fe:141:27)
    at callWithNuxt (nuxt.mjs?v=184e88fe:146:12)
    at router.mjs?v=184e88fe:106:1

[BenjaminOddou]

@Maxp777 @pinia/nuxt module contains pinia by itself. The problem is that

import { defineStore } from 'pinia'

point to '/node_modules/pinia/dist/pinia.mjs'.

That's why we need to use an alias to point to the right pinia location

[mittci]

Two pinia, double effect :)
So if I put alias I can remove pinia from package.json (or I will have troubles like you)

[BenjaminOddou]

I don't have any troubles with pinia (check my portfolio) 😉. And yes the best is to remove pinia from package.json IMHO

repository of my portfolio

[abdonrd]

I just see that @pinia/[email protected] change buildModules to modules.

Updated and now it's working for us!

[mittci]

https://nuxt.com/docs/migration/configuration/#migration-1
a ha ha ha buildModules is deprecated in nuxt 3, but you put it here

[Vivi-Ornitier]

I get the below error when I run the test. $hello is plugin.
It didn't happen in rc.13, did anything change in rc.14?

TypeError: _ctx.$hello is not a function

.vue

<template>
  <div>{{ $hello() }}</div>
</template>

[manniL]

Hey! Could you kindly create an issue and provide a reproduction? 🙏

[vedmant]

I see that 'autoImports' was removed, how do I disable auto imports now? I have custom setup where auto imports are not used as it causes inconsistent code, so there is no need to spend any resource generating this auto import files.

[oooredooo-bit]

[harlan-zw]

Use v3.0.0, try removing the module vuero

[harlan-zw]

This is not the correct code for a module, check how other modules use it

[oooredooo-bit]

Thank you @harlan-zw

[hjleee93]

I got this error after update from rc11 to rc14
I deleted all node_modules and yarn.lock, still i got this error.

`Cannot start nuxt: this.addPlugin is not a function 17:07:03

at module (node_modules/cookie-universal-nuxt/lib/module.js:10:8)
at installModule (node_modules/nuxt/node_modules/@nuxt/kit/dist/index.mjs:416:9)
at async initNuxt (node_modules/nuxt/dist/index.mjs:1827:7)
at async load (node_modules/nuxi/dist/chunks/dev.mjs:6779:9)
at async Object.invoke (node_modules/nuxi/dist/chunks/dev.mjs:6840:5)
at async _main (node_modules/nuxi/dist/cli.mjs:50:20)`

[manniL]

That's on the author of cookie-universal-nuxt to fix ☺️