Broken links after moving Vite plugins out of core

[Pezmc]

Describe the bug

Several Vite ecosystem pages link to packages within the core repo pages directly e.g:

• https://github.com/vitejs/vite/tree/main/packages/plugin-vue
• https://github.com/vitejs/vite/tree/main/packages/plugin-vue-jsx
• https://github.com/vitejs/vite/tree/main/packages/plugin-react

Pages include:

• https://www.npmjs.com/package/@vitejs/plugin-vue?activeTab=readme
• https://vitejs.dev/plugins/

Since #11158 was merged these links now 404. It looks like the docs have been updated in GitHub but the website / npm have not been updated yet.

Currently after, hitting a 404, a user has to dig through Github issues to find the updated URL's since the packages are no longer linked from the readme.

Reproduction

https://vitejs.dev/plugins/

Steps to reproduce

The above pages link to the packages in core, which have now moved separate repos under https://github.com/vitejs/

e.g: https://github.com/vitejs/vite-plugin-vue/

Possible fix:

• Temporarily add links to the other repos to vite core readme, to make it easier to self solve
• Redeploy the Vite docs website
• Long term, update npm.js and the docs to link to the other repos directly

System Info

n/a

Used Package Manager

npm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[ArnaudBarre]

Vite docs are now up to date.

@patak-dev maybe we should keep two-lines Readme in core for a while to help people that are clicking on links from other sites/blogs?

[patak-dev]

I thought about that, it is a pitty that GitHub doesn't give us a per-folder redirect to another repo. I think having the extra packages/... may also be confusing and we will end up with the same issue once we remove them. IMO the best is to try to get the main sites to change the links.

[bluwy]

Closing as this is fixed now in the docs