feat: allow plugins to define routes #879
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This feature allows plugins to define their own routes that go through the Vite server.
Previously, if you wanted to write a plugin that creates routes and share that plugin across sites within a monorepo, you needed to manually add routes in the
routes/...dir that load and provide the routes.Now, a plugin can write its own
routesto construct routes that go through the Vite server. So, plugins can create pages that useimport.meta.glob, provide API routes, etc. without copying the routes into the project dir.The idea is that plugins can be authored for common utilities like design system galleries, custom localization integrations, a custom issue tracker app, etc. -- all using the Vite server without copying the routes files.