Barthélémy Ledoux

The main conflict seems to be about `NativeElements`/ `IntrinsicElements`. Another solution might be to share the definition of the `NativeElements` in a separate package, then have React and Vue typings...

Hello @DanielRosenwasser, Does TypeScript have a solution to deal with JSX ambient types conflicting? I tried using the `"types":[]` trick without luck. I tried using the `paths: {}` trick to...

@martinoppitz I do not understand. Do you mean that preact typings are different from react typings? What do you suggest I do in a monorepo that has both react and...

React and VueJs are not in the same package in the above monorepo.

Thank you @martinoppitz, I understand your disliking for monorepos. They can create monoliths that are long to clone and even longer to install. In our case though, the vue-next monorepo...

Thank you @yyx990803, this will help a lot. If you are looking for someone to bounce ideas with, ping me on VueLand. I'll be happy to show enthusiasm or constructive...

This issue closes the one on awesome-vue3 https://github.com/blacksonic/awesome-vue-3/issues/30

@Scrum There are a couple of features I like about having it in an issue. - Comments are easy - Links to issues are real references (for back linking and...

@tudorels I will add it right now.

@tudorels do you have a vue 2 compatible library? And some migration docs?