Ido Schacham

+1

In fact, it seems like the wrong types are generated. I'm using Gatsby + Contentful. When I look at the possible GQL queries via http://localhost:8000/___graphql for some `allContentful*` query, then...

@adrian13val Seems like configuring Vite's target build indeed solves the issue when building. However, it still reproduces when running the dev server, this configuration seems to have no effect there

Plus one, also reproduced this, albeit without Next.js, rather with a client side application using React 18 and Vite 5.1

+1

> I believe I've found a workaround that works consistently for us: > > ```ts > await page.waitForLoadState('domcontentloaded') > await page.waitForLoadState('load') > await page.waitForLoadState('networkidle'); > await page.waitForFunction(() => > document.readyState...