Nick Taylor

We migrated towards preact-testing-library, https://github.com/forem/forem/pull/8224

> I don't think we have a way of handling different versions, do we? Presumably this will cause the reverse problem for older versions of Vite. I guess that's less...

I'm going to put this back to draft for the moment, because I'm not sure if this framework is meant to only be used with our Edge starter, https://github.com/BuilderIO/qwik/tree/main/starters/servers/netlify

I'm going to also validate if this affects the frameworks that use vite and have their own framework info configuration, e.g. Hydrogen.

I've added it to the backlog

I think @ascorbic added these back in https://github.com/netlify/netlify-plugin-nextjs/pull/1479?

From @ascorbic > This can probably wait until the Edge router is done.

I believe that this is fixed by https://github.com/netlify/pillar-runtime/issues/387 @bhavana-netlify or are we waiting to hear back from the Enterprise customer still?

Just following up on my previous comment @bhavana-netlify.

I'm looking into all of the following: There are a few things going on. I'm getting an HTTP 502 in some E2E tests because https://deploy-preview-1291--netlify-plugin-nextjs-demo.netlify.app/old/ results in a function crashing....