Marcelo Higa

i have the same problem.......

@solufa any updates on this?

A bit old but a workaround is to use nextjs resolveHref function you will get the full href path string https://github.com/vercel/next.js/blob/b8ae447b0fdc12553b4eacd26595e4054ffcf415/packages/next/shared/lib/router/router.ts#L223 ```ts import { resolveHref } from 'next/dist/shared/lib/router/router' const paths...

@SichangHe the config above should work fine.

did one fixed it ?.....

@kramer65 i see. i've been waiting this for ages, if anyone has the fix please share with us! thanks!

@stefaang thanks im gonna try thought it!