Marcin Kotlicki
Marcin Kotlicki
#1027 has this been already considered?
For people needing a fast switch with minimal breaking changes -> https://github.com/fortedigital/nextjs-cache-handler
@harry-gocity fyi even though most users who decided to go with https://github.com/fortedigital/nextjs-cache-handler use app router, the library has recently had compatibility fixes for Next 15 with pages router as well.
Well, Next 16 is around the corner - this package seems pretty much dead.
This is still an issue in Next 15.1.6. Using `loading.tsx` and `redirect` in `page.tsx`
@danielmahon please look into this as this bug is mentioned in multiple issues across your plugin, netlify and gatsby itself.
@mrkaluzny comments resolved, could you have a look?
I created a temporary workaround, this is a decorator that we wrap the CacheHandler with: ``` const DecoratedCacheHandler = CacheHandlerDecorator(CacheHandler); module.exports = DecoratedCacheHandler; /* * TODO: Remove this after issue...
I have just noticed that there is no support for Next15 yet... #969
@neilhem we have already solved this problem in https://github.com/fortedigital/nextjs-cache-handler. It's related to buffer-string breaking change in Next15. This part precisely https://github.com/fortedigital/nextjs-cache-handler?tab=readme-ov-file#3-buffer-string-decorator