feat(vite-plugin-nitro): add support for API routes without middleware/proxy #1621
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for analog-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for analog-blog ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for analog-ng-app ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for analog-app ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
6e02afa to
6c1c4e6
Compare
osnoser1
approved these changes
Feb 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Checklist
Closes #1494
What is the new behavior?
API routes have been defined using the
src/server/routes/folder convention and are prefixed with/apiby default. This has some built-in limitations with having to use middleware or a proxy to re-route API in development when mounted under the/apipath in the Vite Dev Server, and then re-routed with the Nitro server in the production build.This also causes issues when using headers and redirects, as they are not applied to the middleware process.
We are moving to using the
src/server/routes/apifolder to explicitly register API routes, which are treated as full/api/*path routes without using middleware or a proxy. This change looks for an explicitly definedsrc/server/routes/apifolder and falls back to the previous behavior for backward compatibility.In the future, we will look into adding an automated migration for existing routes to mitigate breaking changes for Analog 2.0.
Does this PR introduce a breaking change?
Other information
[optional] What gif best describes this PR or how it makes you feel?