Albert Brand

If you pass an object via the `scope` prop (see https://cinwell.com/vuep/#/?id=javascript-scope), every property of that object is accessible as a variable in code. Getting data out is AFAIK not possible.

There's indeed no API that lets you do this yet. In my blog I've created a solution for such a question: https://medium.com/xebia/theming-in-vue-single-file-components-7b88eaa0eb6e (or specifically https://gist.github.com/AlbertBrand/9697ba4cd11929f1d38204e37220115b)

Is that an iOS screen? 😃

Yes. But keep in mind that each component you render in v-for will trigger a separate network call. Also, if the list is often updated, this is again trigger individual...

Can you change the README so it reflects these new properties?

I've not used Nuxt before so I'm not sure if I can help. I can give it a try, but I'm a bit limited on time currently.

Allright, tried to follow above steps and saw that Nuxt is still on core-js 2.x while I just upgraded vue-async-function to core-js 3.x. Also, `@vue/composition-api` doesn't support SSR yet so...

Sounds like a good idea, I never liked the 'magic' of the accept header anyway. It's there because this implementation is loosely based on the hooks API of [React Async](https://docs.react-async.com/getting-started/usage#with-usefetch).

True, I should've used an upward dep. It's only a warning though.

I've also seen this issue. It seems the following flow happens: **Serverside** - The plugin registers an `supabaseClient.auth.onAuthStateChange` callback and calls `await supabaseClient.auth.getSession` - Session contains an expired refresh token,...