You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@aqos156 Thanks for reporting this bug -- that was quite the oversight on my end. I've updated the specs to catch this and published v2.2.3 with the fix.
Describe the bug
When
usePathname
is used within the codebase the return typeRouteLiteral
is being resolved toany
.However, everywhere else (that I have checked) the
RouteLiteral
is being resolved correctly.Workaround
I have disabled generating types in production builds and manually removed the
usePathname
type override fromnextjs-routes.d.ts
.Context (please complete the following information):
pages directory,app directory,or both?or the CLI (npx nextjs-routes
)?The text was updated successfully, but these errors were encountered: