Compiler errors when building about listr2 HOT 11 CLOSED

I ran into this issue too when building locally and rather than trying to fix all the types I just skipped the lib type check with this typescript compiler flag

"skipLibCheck": true

from listr2.

I have seen some tsc references build errors but this is like complaining about all the types. I will have a look but do not have much idea about the ETA nor where to start.

from listr2.

Can you confirm that you have only one version of listr in your monorepo? But even though you do have two it is still too much errors.

And can you confirm whether it builds without the references and manually building them first.

from listr2.

tried it. still not building.

tsserver is reporting all of the same issues as the compiler though.

from listr2.

Also checked to confirm that only one version was available. The only version I can find is 3.0.1 in my root node_modules

from listr2.

I am bit baffled about this. Havent had any progress with it.

from listr2.

I found it to be because of the highly customized tsconfig in the repo. When I was contributing to the project I couldn't even get the @<path> to resolve correctly, nor could I get the examples to build without some intervention

from listr2.

I am also having issues with the type declarations, I created an example by copying the examples directory and updating the imports to use the npm package. I created a workflow to show the errors.

from listr2.

Okay thank you for reproduction. I will have a further look at it. The problem seems to be assigning default renderer for type completion again. I guess i have to find another way to do that part. In the mean time you can disable library type check in the tsconfig file if you wish.

from listr2.

On further notice I have realized that it does not return the static options and per task options properties of renderer by generics. Earlier versions supposedly returned rendererOptions and per task options utilizing generic types. I will go back and take a look which update did broke it.

from listr2.

🎉 This issue has been resolved in version 3.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from listr2.