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
This bug is about vscode type hints. Because I get no type hints at all on Stackblitz, it appears to be required to download the stackblitz repo and check it out manually, I'm afraid. Here are the steps required after download and extraction:
run npm i and npm run prepare
hover ref in line 8 of src/runtime/components/Test.vue and see that there are no type hints popping up
uncomment the 4th line in playground/nuxt.config.js and run npm run prepare again
see that the type hints from before are now shown
I'd expect the type hints to show right away. @danielroe once fixed this in nuxt/framework#7726 I believe, but apparently there is more to it, maybe a misunderstanding.
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered:
That PR led to unwanted behaviour in monorepos so we now have a specific option for module authors and others who want types to be applied across a workspace:
Environment
Linux
v16.14.2
3.0.0
1.0.0
npm@7.17.0
vite
-
-
-
Reproduction
https://stackblitz.com/edit/nuxt-starter-qspr4q?file=src%2Fruntime%2Fcomponents%2FTest.vue,playground%2Fnuxt.config.js
Describe the bug
This bug is about vscode type hints. Because I get no type hints at all on Stackblitz, it appears to be required to download the stackblitz repo and check it out manually, I'm afraid. Here are the steps required after download and extraction:
npm i
andnpm run prepare
ref
in line 8 ofsrc/runtime/components/Test.vue
and see that there are no type hints popping upplayground/nuxt.config.js
and runnpm run prepare
againI'd expect the type hints to show right away. @danielroe once fixed this in nuxt/framework#7726 I believe, but apparently there is more to it, maybe a misunderstanding.
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: