Ryan Christian

Any chance you have a reproduction? I think we're just missing an alias here, though I'm not a Next or Jest user myself.

Most of these seem to be because you did not copy the full install command. Yes, if you strip out `next`, you're going to get warnings. Same goes for the...

Sounds like wonky resolution with Yarn 2 if it thinks `next` isn't provided when you've already installed it.

This seems to be another one of Yarn 2's infamous problems. You'll either need to ignore the warnings (as they're, at least mostly, wrong) or move to a tool that...

@merceyz Yarn 1 does not give the same complaints, at least not fully. The warning against `next` being provided certainly doesn't show up, beyond that, I didn't look too closely,...

> No, this is entirely intended. Something can be intentional and still an error to the larger community. >It's not an "infamous problem", it's a documented behaviour. Behavior being documented...

Hm, I wonder if that's more of a failing of our Preact-CLI docs than the Typescript docs? We're admittedly missing references to a few official templates on CLI's [Getting Started...

Sorry, what does this fix? Seems to all be working as-is.

> Due to the correct type resolution now thanks t the `@types` alias, we can now ignore the `skipLibCheck` Hm, I don't think this is the case. Mileage may vary...

And that's a great idea actually, having a bunch of Preact projects set up with various React tools as a means of testing, even if it's just quick eye-balling for...