Skip to content
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 6 announcement post #18738

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Conversation

patak-dev
Copy link
Member

Description

Announcement blog post for Vite 6. Feel free to commit modifications.

About the Main Changes section, currently it links to each section in the migration guide. At least for the features, we could expand with an example if you prefer that.

@patak-dev patak-dev added the documentation Improvements or additions to documentation label Nov 22, 2024
@patak-dev patak-dev added this to the 6.0 milestone Nov 22, 2024
![Vite 6 Announcement Cover Image](/og-image-announcing-vite6.png)

It has been an eventful year. Vite adoption keeps growing, with npm downloads per week jumping from 7.5 million to 16 million since the release of Vite 5 a year ago. [Vitest](https://vitest.dev) is not only being chosen by final users but is also starting to form an ecosystem of its own. For example, [Storybook](https://storybook.js.org) has new testing capabilities powered by Vitest. New frameworks have joined the Vite ecosystem. Among others: [TanStack Start](https://tanstack.com/start), [One](https://onestack.dev/), [Ember](https://emberjs.com/). Web frameworks are innovating at an increasingly faster pace. You can check out the improvements folks have been doing at [Astro](https://astro.build/), [Nuxt](https://nuxt.com/), [SvelteKit](https://kit.svelte.dev/), [Solid Start](https://www.solidjs.com/blog/introducing-solidstart), [Qwik City](https://qwik.builder.io/qwikcity/overview/), [RedwoodJS](https://redwoodjs.com/), [Remix](https://remix.run/), and the list goes on.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With the big React Router v7 release yesterday, I imagine it's helpful to the remix team if it's React Router that's listed here rather than Remix. It would align with the other entries naming the server stack rather than the teams behind. Remix is still mentioned below in the Bolt section too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants