You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have identified an issue with the typings on $fetch where the types clash with the contents of the dist folder if you have run npm run generate.
Using the repo attached initial install will show both the useFetch and useAsyncData composables are typed.
Then if you run npm run generate you will see the useAsyncData composable no longer has a typed data ref. This is because $fetch's types are now conflicting with something in dist.
Before running npm run generate:
After running npm run generate:
You can confirm it is indeed the dist by deleting it and reloading the typescript server results in the types returning.
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered:
Environment
Darwin
v16.17.0
3.0.0-rc.13
0.6.1
npm@8.15.0
vite
-
-
-
Reproduction
https://github.com/GerryWilko/nuxt-fetch-typing-issue
Describe the bug
I have identified an issue with the typings on
$fetch
where the types clash with the contents of the dist folder if you have runnpm run generate
.Using the repo attached initial install will show both the
useFetch
anduseAsyncData
composables are typed.Then if you run
npm run generate
you will see theuseAsyncData
composable no longer has a typed data ref. This is because$fetch
's types are now conflicting with something indist
.Before running
npm run generate
:After running
npm run generate
:You can confirm it is indeed the
dist
by deleting it and reloading the typescript server results in the types returning.Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: