Performance improvements for Intellisense #1689
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Was digging again thru why Intellisense is so bad for me, and found this gist : https://gist.github.com/casamia918/dafd630a1cdd81935a4587297acaae00. TBH I am not sure it's helping, but it doesn't hurt and I like that we are more consistent in importing from mui/material instead of mui/system. And when I run
tsc --generateTrace trace, I can see there's about 1,000 less lines of types to generate.Original github issue: microsoft/TypeScript#34801. It seems like MUI types are a big slowdown. It might also help to replace all icons with ones from react-icons instead of material-icons... not too easy to do, though