-
-
Notifications
You must be signed in to change notification settings - Fork 9.1k
Closed
Labels
🍰 p2-nice-to-havePriority 2: this is not breaking anything but nice to have it addressed.Priority 2: this is not breaking anything but nice to have it addressed.✨ feature requestNew feature or requestNew feature or requestscope: types
Description
Version
3.0.0-beta.3
Reproduction link
https://github.com/elevatebart/vue-next-react-ts-conflict
Steps to reproduce
# Checkout the repo
git checkout https://github.com/elevatebart/vue-next-react-ts-conflict.git
# Install all modules
npm ci
# run tsc
npm startThe errors you see in the console are due to React and Vue TSX accepting different values.
What is expected?
When migrating from React to Vue, types should not fail without installing them.
What is actually happening?
it fails at compilation
JSX types could be made a separate package: @vue/jsx-types.
This way, types would not systematically be installed.
Devs could install the runtime they need without the typings.
The transition would be easier.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
🍰 p2-nice-to-havePriority 2: this is not breaking anything but nice to have it addressed.Priority 2: this is not breaking anything but nice to have it addressed.✨ feature requestNew feature or requestNew feature or requestscope: types