-
-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nuxt is still under active development? #29730
Comments
Would you be able to provide a reproduction? 🙏 More infoWhy do I need to provide a reproduction?Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making. What will happen?If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritize it based on its severity and how many people we think it might affect. If How can I create a reproduction?We have a couple of templates for starting with a minimal reproduction: 👉 https://stackblitz.com/github/nuxt/starter/tree/v3-stackblitz A public GitHub repository is also perfect. 👌 Please ensure that the reproduction is as minimal as possible. See more details in our guide. You might also find these other articles interesting and/or helpful: |
Let the bullets fly for a while. |
@xjccc any idea if there's something going on? |
Absolutely under active development. I've been in SF for GitHub Universe. What makes you think it's not under active development? 🤔 |
✔ Regular commits |
It was a genuine question, if you guys say all is good, then I guess all is good 👍 |
@ronenteva That's totally fine - but how did the question came up in the first place? |
I think he means that there's no commits from maintainers from these past days. |
It is not uncommon for successful dev teams behind great projects to get an investment or something that shifts their attention somewhere else. If you exclude deps and docs updates, it seems that there were significantly less commits in the last few weeks than there were before. Nuxt 4 was expected to be released in June, and in September the release date simply became "to be announced". Also I know you aim to publish a patch release every week or so, but there hasn't been one in like 6 weeks. |
As far as those specific points, we're currently waiting on Nitro v2.10 for our next minor release, which has been expected imminently for a while. You can track the outstanding TODOs in #29077. We are waiting on Nitro v3 for the Nuxt v4 release. You're right that we've discussed it often in the Discord office hours and on Twitter, but I understand you might not have heard that. Nevertheless, it's also normal for team members to decrease at times throughout the year, for example if they are speaking at conferences, or focusing on a different project in the Nuxt ecosystem. Next time I suggest asking about an ETA rather than asking if the project is under active development - which it clearly is. Regardless of your (good) intention it comes across as a bit of a slap in the face to people who are coding, answering issues, commenting on pull requests and merging PRs. |
Hearing someone questioning if one of most active frameworks I know is under active development feels so weird. Especially in terms of what we had happening in Vue not so long ago (300 PRs, 400 PRs, 500 PRs). You could also say Vue is dying even now - but to do that you also have to close your eyes and ignore the whole picture, which includes Vite, Rolldown and Vapor.
Honestly in current state of the framework you don't really need Nuxt 4. We were waiting for Summer release only to plan for upgrade window in our company - but since we have compatibility flags we can do them instead. Right now, I want those huge h3 improvements :D Also, Nuxters are one of the most transparent folks I know. You can easily get what to expect in Nuxt 4 PR. I do agree that Nuxt 4 ETA communication is not that clear, but if you follow Nuxt history a bit more, current situation is much better than what we had with Nuxt 3 release and it's nice to see team learning from mistakes, including migration preparations. Speaking of decreased commits count: it's worth remembering that this repository is only a part of whole ecosystem. Here's some of contributors October activity. Sometimes I'm worried about how are they even managing to work like this every month. Despite everything, we had many UnJS releases that are preparing the ecosystem for Nuxt 4. Keep up the good work, team💪 |
It's been very quiet here recently, did something happen behind the scenes?
The text was updated successfully, but these errors were encountered: