-
Notifications
You must be signed in to change notification settings - Fork 980
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fresh Typescript Project Throws Errors #5189
Comments
Hey @brettdoyle44, thanks for reporting this! Would you mind running two commands and pasting the output here to confirm some things? I think this may be the same issue as #5104 which means our latest fix here #5165 didn't work.
The output I see is:
|
Thanks for reporting @brettdoyle44 Turns out the whole of the internet using React + TS is experiencing this, but I did have it resolved — apparently not for all cases. There are a lot of Issues open on DefinitelyTyped. I'm following this one by the Microsoft Team: microsoft/DefinitelyTyped-tools#433 Gah, this behavior is so frustrating... 🤬 Also, it works after upgrading to canary. Why?!? Reproduction steps to resolve with Canary version
The canary version has the same dep resolution as the latest. The upgrade command runs Ah, there might be a more recent version of the packages... I could try that as well. And/or there might be something else about canary that makes it resolve correctly -- I'll find out with an RC today. |
got it. will fix via 1.0.2 coming asap |
@thedavidprice Upgrading the project to Canary worked for me. I am just starting on my project, so should I wait for v1.0.2 to start fresh project? |
Hey @brettdoyle44 |
Overview:
When creating a new redwoodjs typescript project it throws errors in multiple files in VSCode. The two biggest are on Router and App.tsx. I have tried to use David's solution in the following forum post, but as soon as I spin up dev the errors return: https://community.redwoodjs.com/t/i-see-red-squiggles-how-to-fix-type-warnings-in-vs-code/2961.
Current versions:
Node v16.13.0
Yarn v1.22.18
Steps to replicate:
The text was updated successfully, but these errors were encountered: