Add exportAssetPrefix config option #2145
Conversation
Github project pages for example, by default, have the root of the page on a subdirectory. It is needed to be able to specify the static asset prefix without changing the way next.js handles next dev/start
| @@ -80,6 +80,11 @@ export default async function (dir, options) { | |||
| hotReloader: null | |||
| } | |||
|
|
|||
| // Static hosted sites sometimes have different url requirements | |||
| if (config.exportAssetPrefix) { | |||
| renderOpts.assetPrefix = config.exportAssetPrefix.replace(/\/$/, '') | |||
There was a problem hiding this comment.
Why can't we simply use the existing assetPrefix option? https://github.com/zeit/next.js#cdn-support-with-asset-prefix
There was a problem hiding this comment.
Because the folder structure and asset path are different on the exported site versus local. Example: github pages project site where it's at organization.github.io/project-name but the files actually live in the root of that project repo. Using just assetPrefix breaks local development
There was a problem hiding this comment.
I see what you're pointing out though with the production check in the config file. does the config function expose any context regarding whether static export is happening or would I need to run my command with NODE_ENV=production? Also I'm good with closing this.
There was a problem hiding this comment.
I think this is related to deploying to a sub folder.
That's something we need to address separately.
|
Closing. |
Github project pages for example, by default, have the root of the
page on a subdirectory. It is needed to be able to specify the static
asset prefix without changing the way next.js handles next dev/start