Allow using getPathname outside of NextJS context

[nevnein]

Right now, getPathname is tied to the NextJS runtime (at least that's my understanding, correct me if I'm wrong) but a type safe url builder based on a static config could be extremely useful even outside of it, I've find myself needing it in tests with different runtime, other packages in the monorepo and so on

It would be nice to be able to export it and import it for use somewhere outside of NextJS, or alternatively having a way to leverage the functionality (which should be only dependent on the config I guess) outside of the NextJS scope

I've taken a look at use-intl but it doesn't seem to solve this problem

[amannn]

getPathname is tied to the NextJS runtime

I don't think that's true, have you tried calling it outside of the Next.js render process? It can be useful e.g. for sitemaps.

Not sure if I'm overlooking something …

[nevnein]

We've tried using it outside of Next and we ran into some module resolution issues, eg. this one in Playwright microsoft/playwright#35162

[amannn]

Ugh, that one's tough. It's related to vercel/next.js#77200, so unfortunately a bundling issue with Next.js.

I've also joined the conversation here: microsoft/playwright#35162 (comment)