Open hongkiulam opened 1 year ago
I had this issue in preview environment on vercel. I was using the vercel preview deployment protection which threw itself in between the middleware call to https://[vercel-preview-domain].vercel.app/_next/static/~csp/csp-manifest.json strictDynamic fetch requests the cspmanifest.json and has no catch for if the response isnt json.
I've reproduced the issue here: https://codesandbox.io/p/sandbox/next-safe-middleware-issue-84-6ywgjy
Still trying to figure out, why the csp-manifest.json
cannot be fetched. It uses the correct URL, I get a JSON back if I paste the URL in the browser.
Did anybody figure out why strictDynamic or strictInlineStyles break the middlewares in production mode?
When I run
npm run build
with standalone mode, followed bynode server.js
to run the application, I get500
when trying to load any page. I've narrowed it down tostrictDynamic
andstrictInlineStyles
because including either of these causes the same issue.Running the e2e in this repo doesn't seem to have the same issue so something in my setup in combination with the package causes the issue? Just not sure where 😓
Package Versions
Middleware file