Support for assetPrefix in Next.js configuration #272
Unanswered
ivan-jancic
asked this question in
Q&A
Replies: 1 comment
-
|
There isn't really a roadmap, but it's open source! Feel free to add it.
Cheers
Mischa
… On Dec 23, 2025, at 1:54 AM, ivan-jancic ***@***.***> wrote:
Hi cdk-nextjs team,
We're evaluating cdk-nextjs for our project and need to configure assetPrefix to serve Next.js assets from a different URL than the base path (specifically for our CloudFront-based gateway architecture).
Is support for assetPrefix on the roadmap, or are there any recommended workarounds for this use case?
Thanks for the great work on this construct!
—
Reply to this email directly, view it on GitHub <#272>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAB33C7XJPOSR7753XHO7NL4DEGOFAVCNFSM6AAAAACP2ULPRKVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZZGI3TKMZZGA>.
You are receiving this because you are subscribed to this thread.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi cdk-nextjs team,
We're evaluating cdk-nextjs for our project and need to configure assetPrefix to serve Next.js assets from a different URL than the base path (specifically for our CloudFront-based gateway architecture).
Is support for assetPrefix on the roadmap, or are there any recommended workarounds for this use case?
Thanks for the great work on this construct!
Beta Was this translation helpful? Give feedback.
All reactions