khuezy

@magiclen `nginx-cache-purge p /data/nginx-cache 1:2 '*' -e '/_next/image*'` this mostly works but only a few of the images are purged, the rest remains and are HITs

I also noticed this when trying to use daisyui custom themes in an email client, which doesn't support `oklch`

Can you reproduce this locally via `standalone` output? Just trying to verify if this is a next standalone issue or a bug somewhere in open-next redirect.

You'll need to apply this patch until the PR is merged: https://github.com/sst/sst/pull/3567 You could try to deploy via `ion` - the redirect might be fixed in v3.

Hi can you specify the `open-next` version and exact next version? Can you also set up a min repo? According to the latest versions `pages`: https://dqijpnhzoveol.cloudfront.net/foo `app`: https://d1rjbhcyvwj9a2.cloudfront.net/foo They both...

A minimum reproduction project on github so we can see what's causing the issue.

@ilyastam can you try upgrading next to 14.2.2, according to the test, it passes: https://discord.com/channels/983865673656705025/1027265626085019769/1230685589926576309 But there might be some edge case in your setup that's causing the infinite loop...

You can join our discussion here: https://discord.com/channels/983865673656705025/1164872233223729152 I think Fly.io is a great choice, and adding Cloudflare to that would be 🔥

> Any progress on this? Not much, for now, you can try using `outputFileTracingExcludes`: ``` outputFileTracingExcludes: { '*': [ '**@swc/core**', '**esbuild**', '**uglify**', 'webassemblyjs', '**sass**', '**caniuse-lite**', "@aws-sdk" ], }, ``` It's...

Something change in the later version of next (not sure if bug or by design.) Using the "**" causes an infinite loop. You have remove the wildcard.