Support base path parameter from next config #79
Conversation
| @@ -23,6 +23,15 @@ export class RenderModule { | |||
| await next.prepare(); | |||
| } | |||
|
|
|||
| const nextConfig = (next as any).nextConfig; | |||
| const nextServer = (next as any).server; | |||
There was a problem hiding this comment.
Depending on Next version (^9 or ^10) nextConfig property may be in a different location. In older Next ^9 we have direct access to it with proper typings. In Next ^10 I wasn't able to find any way to access the config from injected Next Server instance, however there is a way to get it from an untyped server property. Tested this on reproduction repo provided in #78 with Next 10.2 and on an enterprise project with Next 9.5.
| ? nextConfig.basePath | ||
| : nextServer.nextConfig.basePath; | ||
|
|
||
| const config = { basePath, ...options }; |
There was a problem hiding this comment.
basePath from RenderModule options has higher priority (in case you might want to override the base path in next.config.js for internal endpoints (eg your Nest application is deployed behind a proxy)).
|
Thanks for the contribution - this looks good to me 👍 |
Changes are made to support both injecting a custom base path through options and pulling base path from local Next config from injected Next Server instance. Explicit base path in RenderModule options is used over the one from Next config if specified.
This PR closes #78.