Summary

A route that previously worked is now throwing a 'No route found' error after upgrading to version 1.136.5. The user suspects a change in routing logic or configuration that affects specific locations. The task is to identify the root cause of this regression and fix it, likely by examining routing definitions or the library's internal handling of route matching.

Skills Required

Files Likely Touched

• packages/router/src/Router.ts
• packages/router/src/Route.ts
• packages/router/src/utils/parseSearch.ts
• packages/router/src/MatchRoute.ts