Skip to content
This repository was archived by the owner on Apr 6, 2023. It is now read-only.
This repository was archived by the owner on Apr 6, 2023. It is now read-only.

Migration to nuxt/nuxt #10147

@danielroe

Description

@danielroe

As a complete rewrite of Nuxt 2, Nuxt 3 was developed in a separate repository: nuxt/framework. Nuxt 3 even has its own documentation on nuxt.com, versus the Nuxt 2 documentation on nuxtjs.org. In development, this helped us move faster but meant less attention on issues for Nuxt 2. It's also a bit confusing.

So in the coming days, we'll be unifying the Nuxt repos into a single repository, nuxt/nuxt. We'll transfer all issues and discussions across, of course, clearly labeling them as to which version of Nuxt they affect. This will also provide us an opportunity to close out issues and RFCs that we've resolved or implemented in Nuxt 3.

This issue exists to track the progress of this move.

You can read more about what we're planning in 2023.


#10147 (comment)

Contributors

If you have an open PR, don't worry. The main branch will stay around for a while until all pending PRs are either closed, merged or migrated across to https://github.com/nuxt/nuxt.

If you need to update your local fork you can do so. You can fork https://github.com/nuxt/nuxt and then run in your shell:

git remote remove origin
git remote add origin [email protected]:<yourusername>/nuxt.git
git remote add upstream [email protected]:nuxt/nuxt.git
git branch -u origin/main main

Metadata

Metadata

Assignees

Labels

chore🧹 p1-chorePriority 1: no change in change code behavior

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions