Hi all,

Recently have been testing on Next v13.4.4 and v13.4.5 an application using Pages Router, configured with output: 'export' and an established basePath: '/subdir'

Have run into an odd scenario where some of the links when navigating result in having the basePath duplicated (added twice) -- the interesting thing is that the URL href (generated HTML) do not exhibit this duplication! However, upon clicking a <Link>, the actual network request contains the basePath multiple times, resulting in a routing error.

Here's what's being observed:

Generated HTML:

<a href="/subdir/path/to/example">Example</a>

...☝️ Click the link 🔗

Generated Request (DevTools > Network):

Request URL:

https://domain.com/subdir/subdir/path/to/example

... basePath is duplicated.


Something to note: When observing the initiator for the request, there is an apparent onClick handler, presumably native to <Link>. You can see in the attached image there are actually two (2)
click event handlers div#__next associated with the link. Interestingly, if the handler denoting useCapture: false is manually removed, the basePath duplication goes away! 🤔

Also, worth noting that while the app is configured for static export, the behavior is reproducible in both development mode and production builds.

❓ Has anyone run into this before? I did some searching and found some older bugs around basePath duplication specific to presence of query params, but the links in question do not contain URL arguments FWIW.