Use absolute URLs for resources when exporting a Next.js build

[ScottRAC]

Summary

Hey, I have a scenario where I'd like to statically export my Next.js app with the resources specified with absolute URLs instead of relative which seems to be the default.

For example, when I use "output": "export" in my next.config.mjs file it might export a section of my HTML file as <link rel="preload" as="script" fetchPriority="low" href="/basePath/_next/static/chunks/webpack-7a434acf1532e782.js"/> but I would require it to instead use something like href="https://www.my-hosting-url/_next/static/chunks/webpack-7a434acf1532e782.js".

The basePath config option has to begin with a / so I can't specify it there.

My solution could be to do a find and replace of the base path and replace it with the appropriate URL after the build completes, but I was seeing if there was a native way to achieve this.

Additional information

The reason for this requirement is all the web content will be hosted on domain-x.com and third party will render just the HTML on their own domain-y.com. The resources would then need to be absolute to point to domain-x otherwise they will be failed to be found on domain-y when they're defined relatively.

[ScottRAC]

Never mind, I then immediately found the assetPrefix config option which is exactly what I needed