You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Goal: I would like a "stable" link to the migration documentation.
Background: I maintain/write documentation, libraries, and posts about front-end that includes Vite.
Context on my goal: I would like to link to the V6 migration guide. Currently, I can only access it at https://vite.dev/guide/migration.html but one day this will point to the V7 migration guide. The Vite website has historical markers for v5 and previous (which is awesome).
Your Suggestion for Changes
"Deploy" a v6 subdomain right now for cases where stable linking/pinning to v6 makes sense (example: migration guide).
(Guess/assumption) Looking at the other sub-domains, I would guess that they are currently branch driven (e.g. main.vite.dev and v5.vite.dev). While we may not want to set up v6 yet, we could maybe just CNAME v6.vite.dev to vite.dev right now or set up a redirect. However, this aspect is purely up to maintainers IF you agree with the use case to stable link "in advance" of the next major version.
Reproduction
N/A
Steps to reproduce
See above.
Thanks for all y'all do!
The text was updated successfully, but these errors were encountered:
Documentation is
Explain in Detail
Goal: I would like a "stable" link to the migration documentation.
Background: I maintain/write documentation, libraries, and posts about front-end that includes Vite.
Context on my goal: I would like to link to the V6 migration guide. Currently, I can only access it at https://vite.dev/guide/migration.html but one day this will point to the V7 migration guide. The Vite website has historical markers for v5 and previous (which is awesome).
Your Suggestion for Changes
"Deploy" a
v6
subdomain right now for cases where stable linking/pinning to v6 makes sense (example: migration guide).(Guess/assumption) Looking at the other sub-domains, I would guess that they are currently branch driven (e.g.
main.vite.dev
andv5.vite.dev
). While we may not want to set upv6
yet, we could maybe just CNAMEv6.vite.dev
tovite.dev
right now or set up a redirect. However, this aspect is purely up to maintainers IF you agree with the use case to stable link "in advance" of the next major version.Reproduction
N/A
Steps to reproduce
See above.
Thanks for all y'all do!
The text was updated successfully, but these errors were encountered: