-
-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
docs: vite 5 announcement blog post #14860
Conversation
Run & review this pull request in StackBlitz Codeflow. |
It seems VitePress was relying on the auto injection of |
Co-authored-by: Dominik G. <dominik.goepel@gmx.de>
I wonder if a mention to the upcoming Vitest 1.0 should be mentioned? I mean the first official stable release of Vitest (which Vite uses) is probably worth mentioning. Also as a side note, I know EOY means End of Year, so many acronyms, but that might not be the case for non-English speakers. I saw this comment in one of Vitest's PR from
Excited to know v5.0 and Vitest 1.0 are both coming real soon :) |
Thanks for reviewing the PR and the suggestions @ghiscoding! Applied both to the blog post |
Description
An initial draft for the Vite 5 announcement blog post. Feel free to commit to this PR to expand some of the main changes, add new features, or rework the wording in any of the other sections.
Note: It seems VitePress dev is currently broken.
What is the purpose of this pull request?