-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
chore(): update typescript to 5.8 #10514
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
chore(): update typescript to 5.8 #10514
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
I wanted to do this, but when i heard that the new version is written in go and is 10x faster i just wanted to wait. |
i hoped TS would grow with better understanding rather than poorer. |
that will take a while unfortunately |
I understand what you mean, but it is the best we get currently in js world |
Is not bad at all, is just a bit less smarter than i expected |
There are a bunch of TS-NOCHECK or TS-IGNORE around the codebase that will need to be re-evaluated to understand if TS offers a way to fix them |
I plan to finish migration of qunit to vitest and also visual to playwright |
Yes i wan't asking you to do so, just to inform that ususally when i bump i go and i look for solutions to old problems to see if they have been included. Is how i learn. For the visual tests there is already a framework is just a matter of moving the functions, i started already but i m not sure of long term stability i m finishing the actions from forks so they all pass, i ll finish my gradient PR and i ll update the website to handle versioned docs in someway, you don't have to do all the tests if you get bored stop |
no worries, I am not a maths guy so I can't really help much with fabrics source code |
I noticed that typescript in fabric is already getting old
This updates to latest one as of now which is 5.8.
There was one type issue that ocurred in image.ts which was because filter was destructured it got implicit
any
type so I had to define it without destructuring (it is still inferred as any because that is how it is typed, it is just that typescript doesn't like implicit any since that is configured in tsconfig)I ran build and tests and everything seems fine