dragons-library

I ran into something similar, and I _think_ I have a workaround. TL;DR: instead of reading from `.next/`, read from `.netlify/.next/`. This feels like a temporary workaround and probably not...

Root issue seems to stem from this behavior in the `v5` plugin... ```js var onPostBuild = async (options) => { await tracer.withActiveSpan("onPostBuild", async () => { await publishStaticDir(new PluginContext(options)); });...

### TL;DR - Clearing cookies in my browser resolved this issue for me. I was hitting this same issue when I added my Proxmox proxy URL. I initially entered `http`...

This rough patch resolves my immediate use case (simple redirects), verified via `patch-package` and deployed to netlify. Probably needs to be fleshed out more to handle all of the NextJS...

I _think_ this is resolved with v5 of the plugin. I updated `@netlify/plugin-nextjs` to `5.0.0` and removed my workaround and all my redirects seem to be working as expected, including...

Just for context, I think the first two are things that "broke" with the 3.5.0 release for anyone that started consuming the esm build of `decap-cms-app`. The 3rd item probably...