feat(vercel): generate o11y routes - #3474
Merged
Merged
Conversation
Deploying nitrojs with
|
| Latest commit: |
2f98621
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://15dadf45.nitrojs.pages.dev |
| Branch Preview URL: | https://feat-vercel-o11y.nitrojs.pages.dev |
pi0
marked this pull request as ready for review
July 14, 2025 15:04
This was referenced Jul 14, 2025
Merged
luc122c
pushed a commit
to luc122c/unjs-nitro
that referenced
this pull request
Jul 17, 2025
pi0
added a commit
that referenced
this pull request
Jul 18, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Resolves #3291
This PR updates the vercel preset to generate aliases and symlinks to the main
__nitro.functo allow distinguishing routes from vercel observability panel.This feature is opt-in via compatibility date (
latestor>=2025-07-15)I will also follow up with a vendor-agnostic new option to allow meta-frameworks like Nuxt to declare their SSR routes, as Nitro does not have knowledge about them. (#3475)
seems working well on fixture