fix: revert well-known/skills to middleware approach #637
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.
#634 broke
/.well-known/skillsendpoints. Nitro's file-based routing interprets.well-known-skills.tsas a filename, generating wrong URL patterns:/:pkg/.well-known-skills/:pkg/.well-known/skills/**Broken URLs (prod):
Fixed URLs (preview):
This reverts to the middleware approach from #630 which uses regex matching to handle the path correctly. ISR caching rules in nuxt.config.ts remain unchanged.
Why two handlers?
Middleware runs on every request, so we need:
defineEventHandler- checks URL match, returnsundefinedfor non-matching paths (passes through to Nuxt)defineCachedEventHandler- only caches matching requestsRoutes could use a single
defineCachedEventHandlerbecause file-based routing only sends matching URLs to that handler.