-
Notifications
You must be signed in to change notification settings - Fork 57
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
Enable incremental typechecking by default #1047
Conversation
Actually, let's enable project cache config too by default. Updating the PR. |
I never tested the project cache config apparently. Is it stable enough to activate by default already? |
I think so. But it'd be good to give it a spin in your project(s) too of course. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great!
Are there any downsides, or unknowns, about turning on the cache?
I mean that's why we have pre-releases anyway, right? Or do you want to release this as stable soon? |
We can do pre-release for a while, sure. Maybe a week or so. But then the big benefit comes from shipping this to stable. |
Enables incremental typechecking by default by changing the name of the prop (so old configs are invalidated) and setting a new default.
I'm sure there are more things we could do with incremental typechecking to make it a better experience, but at this point it's such a magnitudes better experience even with the small issues it might have. Enabling by default will make the experience better for everyone by default, and if issues surface we can fix them.
This also enables the
projectConfig
cache options, that dramatically reduce latency in certain scenarios.