Route-matcher is not matching the most specific rule
thezzisu opened this issue · comments
Environment
node: v18.14.1
radix3: "radix3@npm:1.0.0"
Reproduction
See https://github.com/lcpu-club/mirror-frontend. Reproduction steps are:
Simple swapping the rules will affect the output.
Originally posted by @thezzisu in unjs/nitro#1033 (comment)
Describe the bug
Route-matcher is not matching the most specific rule.
Additional context
See unjs/nitro#1033 for more details.
Logs
No response
I'm not sure issue is with radix3 matcher. Nitro prerenderer is not using radix3 (and that's the issue itself :D) ~> unjs/nitro#1078
Appologies. There was an issue only with matchAll. Solving with #45