#next.config.js CORS headers not present for `/_next/static` assets from migrating from next 12 -> 14

2 messages · Page 1 of 1 (latest)

forest fable
#

Hey,
having trouble with upgrading from next 12.3.4 --> 14.2.4 (tried different minor/patch releases) that assets via /_next/static no longer use the headers defined in next.config.js around CORS headers. I'm serving certain "public" folder and next.js generated assets via different subdomain via assetsUri so CORS headers are important for it . Went trough all release logs and docs and don't see any mentions about this regression.

So I'm not sure if expected or a bug?

opal flameBOT
#
Post created!

🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord

🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in id:customize

✅ You can mark a message as the answer for your post with Right click -> Apps -> Mark Solution
(if you don't see the option, try refreshing Discord with Ctrl + R)