Nuxt 3.0 stable

[pi0]

We are thrilled to announce the first stable version of Nuxt 3.0.0 ✨

Nuxt 3 is a modern rewrite of the Nuxt framework based on Vite, Vue3, and Nitro with first-class Typescript support and the result of more than two years of research, community feedback, innovation, and experiment to make a pleasant full-stack Developer Experience for Vue development to everyone.

• ✨ Release Announcenment
• 🐦 Tweet
• 📝 Changelog

[atodd]

Thank you Nuxt team! Very excited to test out the first stable build!

[chrisbbreuer]

Congratulations! This is amazing! 🍾

[miracleonyenma]

Awesome!!!! 🎉🎉

[vanling]

Congratulations on release and the new nuxt.com domain :D

[hausg]

Congratulations !!!

[vinayakkulkarni]

Can't wait to get my hands on it :)

[thomasbnt]

Congrats 🍾🚀🚀

[mrleblanc101]

@pi0 Any reason why @nuxtjs/i18n is not on the official roadmap ?
But there is nuxt/translations on the roadmap which is only the documentation translation and not the translation module itself ?
@nuxtjs/i18n is an essential module for many people.
I know it's a community module, but it's still under the @nuxtjs namescpace and is as important as @nuxtjs/auth imho which is on the roadmap.

[pi0]

The roadmap in docs is focused on features we plan to partially add to either core or built-in dependencies.

@kazupon is hardly working on i18n support Check intlify/vue-i18n-next and intlify/nuxt3.

Discussion: https://github.com/nuxt/framework/discussions/9066

[sadeghbarati]

https://v8.i18n.nuxtjs.org/

[arnauddoub]

Congrats ! 🎉

[insru]

Congrats! Amazing project :)

[StanleyMasinde]

Great job!

[Kyriakos-Michael]

As an old man said, the Nuxt big thing!

[CodyBontecou]

Huge release today. Great job to the Nuxt team!

[AllanOricil]

Amazing work. Thank you

[FileSoft-us]

Let's go baby

[ben890524]

Congratulations 🎉

[kotering]

Congratulations!
I'm looking forward to implementing new applications with Nuxt3.

[MuhammadKhizar7]

Congratulations!

[mittci]

[Redemption198]

Don't use this discussion to post issues, it probably won't be noticed. Open an issue instead, before that try to run npx nuxi upgrade -f and see if it solves your issue.

[mittci]

all is ok, simply useBody has been renamed to readBody

[Redemption198]

oh ok

[yeonjulee1005]

Congratulations! 💯

[modelair]

Congrats!

[favourwright]

I only noticed when I visited v3.nuxtjs.org documentation and was redirected to nuxt.com two days ago...
this release definitely warms my heat♥

I saw a PR relating to default scroll behavior
question: is the scroll behavior now fixed and we don't need to use /app/router.options.js

[zavvla]

@pi0 Congratulations!!!

Everyone was really looking forward to this day =)
Tell me, will there be documentation for other languages, as it was with the second version?

[ka-zii]

up up 🎉 🎉 !!!!

[pagamini]

i'd like it😄

[wikanonymous-dev]

Congrats!!! 🎉

[Disorrder]

hype hype hype!!! 🎉
Thanks for perfect framework!

[nazarepiedady]

When will be it possible to start translating the documentation to other languages?

[nazarepiedady]

@danielroe do you have an answer to my question?

[danielroe]

Currently @pi0 is planning/working on this. See https://nuxt.com/docs/community/roadmap:

nuxt/translations#4 (request access)

A collaborative project for a stable translation process for Nuxt 3 docs. Currently pending for ideas and documentation tooling support (content v2 with remote sources).

[vedmant]

When we can expect documentation for Options API usage with Nuxt 3?

[danielroe]

Here you go: https://nuxt.com/docs/api/utils/define-nuxt-component#definenuxtcomponent

[vedmant]

@danielroe There is no examples of how to use things like route params, runtime configs, redirects, errors, API usage (axios/fetch), Vuex migration, Pinia usage, cookies, layouts, basically everything that was moved to use* compostables.

[InFecTie]

@danielroe is there already better documentation for options API migration from nuxt2 to nuxt3 like asked above?
'....API usage (axios/fetch) and basically everything that was moved to use* compostables.'

Doing a migration with a big solution from nuxt2 is still a pain in the ass and very demotivating to actually transition to nuxt3

[vedmant]

Yeah, when Vue introduced composable API some devs decided that options API is deprecated and switched to composition, but that's not the case, options API was always superior in terms of maintainability and code quality. I move my projects to Nuxt 3, but keep all in options API, however lack of documentation for options API in Nuxt makes this Nuxt incomplete and kind if forces people to use composition API, which is a big mistake.

[noopurphalak]

Amazing work guys...the hard work as finally paid off for you guys...!!! Can't wait to play around with nuxt 3...