Adam DeHaven

@enkot I'm trying to figure out where the interface needs to be modified; glad to help if you want to take a look

@enkot just bumping this and https://github.com/enkot/nuxt-open-fetch/pull/53 again if possible? Let me know if I can provide more info

The code I have in the original post works in v2 when the page is initially rendered via SSR. _It's hard to show a full reproduction as the issue arises...

@harlan-zw I've updated with a reproduction: https://stackblitz.com/edit/github-pfsubbgy?file=app.vue

> It's possible this worked in v1 as there was an arbitrary delay when flushing the tags (around ~10ms), in v2 it just attaches to `nextTick()` so the renders are...

If I update the composable to add an artificial delay alongside `computedAsync` from `@vueuse/core` it seems to resolve the issue for me: ```typescript import type { ComputedRef } from 'vue'...

@enkot this allows proper interfaces for non-`200` responses, e.g. to support something like this: ```typescript // Assume this endpoint returns a `201` response code const myApp: MyClientResponse = { //...

@enkot this PR should resolve 😄 https://github.com/enkot/nuxt-open-fetch/pull/89

Browser testing via `@playwright/test` works for me; if you can provide a reproduction I can take a look at what you're missing. (I'm assuming you're wanting to run tests via...

@enkot is there anything I can do to help move this PR along, or adjust as necessary?