-
-
Notifications
You must be signed in to change notification settings - Fork 442
Move volar to @vuejs org #811
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
Comments
Thank you for your suggestion, but for these reasons I don't think it will be done for the time being.
I hope that this can be done perfectly. The good news is that I will start developing volar full-time in February, so the timetable for volar will not keep on postponed. |
Looking forward to it. Thx |
We didn't move it in v1.0 because Volar itself became a framework, but we may move https://github.com/johnsoncodehk/volar/tree/master/vue-language-tools into vue org. |
The second time to reopen this. 😅 (See #2293 (comment)) |
Done. |
Hii @johnsoncodehk, couple of days back Pinia from @posva was moved to @vuejs org. It's a great news and also makes sense a lot. I think it would be great if Volar also moved to @vuejs org. Volar is recommended as the official VS Code extension for a while now and not only VS Code, many other text editors are also leveraging volar to provide language support for Vue. This was not possible not a while ago. I strongly feel Volar deserves a place in @vuejs org for better community understanding of the Vue tooling setup.
Thank you for your hard work.
Sorry I was unable to figure out where to post this request, so I ended up posting it here.
The text was updated successfully, but these errors were encountered: