-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing storybook breaks Typescript JSX types for Vue3 (Vite project) #16213
Comments
Can confirm this issue. |
can @types/react be an optional dependency instead? |
A simple reproduction from a real project: https://github.com/euaaaio/repro-storybook-vue-volar-jsx |
+1 I've got the same issue! |
Using vuejs/language-tools#552 (comment) {
"compilerOptions": {
"target": "esnext",
...
"lib": [
"esnext",
"dom"
],
"types": [
"vite/client"
]
},
"include": [
"src/**/*.ts",
"src/**/*.d.ts",
"src/**/*.tsx",
"src/**/*.vue"
]
}
|
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks! |
This may help |
Hi, can anyone confirm if this is still an issue in the latest version of |
I believe this is now fixed in the latest storybook 7.0 versions. I'm going to close this out to try to keep things organized, but let me know if you're still having trouble and we can re-open. |
This issue has reappeared since version 7.2 ··· |
Describe the bug
After installing Storybook in a Vue3 Vite project, the project no longer builds due to JSX type conflicts. After installing storybook using the recommended command, the
npm run build
script produces these errors:To Reproduce
My reproduction repo is here: https://github.com/jmeyers91/vue3-ts-storybook-error
Clone it and run
npm install; npm run build
to reproduce.You can also re-create the repo and reproduce the error by running these commands:
System
The text was updated successfully, but these errors were encountered: