useAsyncData/useFetch types do not reflect pick changes anymore about nuxt HOT 8 OPEN

Hi @manniL . I'm the guy who wrote the comment in YouTube about this issue. Thanks for taking the time to report this issue. I have like 68 error messages like this in my project since I updated from 3.8.2 to 3.9.3 and have no clue on how to get rid of them ^_^U

from nuxt.

This appears to be an issue just with pick as transform works fine (FWIW):

const { data } = useAsyncData(() => Promise.resolve({ data: { test: 1 } }), {
  pick: ['data'],
  // transform: data => data.data,
})
const test = computed(() => data.value?.test)

Looking to reproduce, this code (with pick) has a type error all the way back to at least v3.6.0 in the Nuxt playground.

from nuxt.

I am not 100% sure if this applies to this issue. But I was able to resolve type errors in our project by explicitly pinning "vue": "3.4.15" after upgrading Nuxt to 3.9.x.

from nuxt.

Start a new pull request in StackBlitz Codeflow.

• nuxt-issues-25443 (Open reproduction)

from nuxt.

@danielroe Attached a repro (that I wanted to put there before, sorry) also showing transform issues I think.

from nuxt.

Would there be no way of having the useFetch return a globalThis.Ref (without using transform or pick) instead of Ref like before?

from nuxt.

https://nuxt.com/docs/getting-started/data-fetching#minimize-payload-size

Is the reproduction code misusing pick?
pick: ['data'] and transform: data => ({ data: data.data }) operate similarly, but repro code seem to be expecting transform: data => data.data.

const { data } = useAsyncData(
  'key',
  async () => {
    return { data: { test: 1 }, foo: 'bar' }
  },
  {
    pick: ['data'],
  },
)

const test = computed(() => data.value?.foo) // Property 'foo' does not exist 
const test = computed(() => data.value?.data.test) // works

from nuxt.

I am not 100% sure if this applies to this issue. But I was able to resolve type errors in our project by explicitly pinning "vue": "3.4.15" after upgrading Nuxt to 3.9.x.

Thanks! Pinning Vue 3.4.15 fixed the issue I was having as well.

from nuxt.