This PR doesn't fully fix #7662, though.

This PR doesn't fully fix #7662, though.

I think the same is for the Vue issue too as it's an error happening in third-party libraries? The issue has an error from tsc but the build should be fine, or maybe that can be fixed too?

skipLibCheck never affects Vite build. So enabling it is meant to fix the type errors.
There are still errors in #7662 after this change.
Maybe it's because the @chakra-ui/* types are written in .tsx rather than .d.ts files (skipLibCheck only ignores .d.ts).

I'm not an expert on either Preact or TypeScript, so I can't provide a solution to the problem.

Ah I see, for #7662 besides setting skipLibChecks: true, I had also installed @types/react and @types/react-dom locally. That's why I didn't see any errors when testing that. I'll make a note in the issue there, and probably ask around of how to setup preact with typescript. Otherwise we could also add the @types too 🤔

@marvinhagemeister maybe you could help us here?

Ah I see, for #7662 besides setting skipLibChecks: true, I had also installed @types/react and @types/react-dom locally. That's why I didn't see any errors when testing that. I'll make a note in the issue there, and probably ask around of how to setup preact with typescript. Otherwise we could also add the @types too 🤔

FYI, if you add @types/react for the preact-ts preset then it will conflict with the JSX typings of the preset (src/preact.d.ts).

I have found some related issues preactjs/preact#2150, preactjs/preact#2222.
But these solutions are not mentioned in docs. https://preactjs.com/guide/v10/getting-started/#typescript-preactcompat-configuration

I have found some related issues preactjs/preact#2150, preactjs/preact#2222. But these solutions are not mentioned in docs. https://preactjs.com/guide/v10/getting-started/#typescript-preactcompat-configuration

Maybe we can apply these solutions in this PR to fix type conflicts?
cc @bluwy @sodatea

Maybe we can apply these solutions in this PR to fix type conflicts?

If you're referring to preactjs/preact#2150 (comment), it looks a bit fragile to me and it's been more than a year since the solution is posted. Maybe there's a better way of handling it now.

I removed the link to #7662 at the meantime. Perhaps we can deal with the preact template later when there's a solution to it.