3 ms·
We're straight TypeScript/ React. We have a pretty large codebase though which no doubt contributes to the issue. The thing is, VIM uses the same language serv
by ogre_codes 6y ago
We're straight TypeScript/ React. We have a pretty large codebase though which no doubt contributes to the issue.
The thing is, VIM uses the same language server and (so far anyhow) doesn't melt down. It seems like the issue is in the Code Helper process itself.
- brundolf 6y agoI have heard of people running into issues with the file-search indexer taking a long time on extraordinarily large projects. The largest project I've used it on was in the thousands of files (excluding node_modules) and didn't have any issues. But I know there are much larger projects out there, so I can't speak to those.
- ogre_codes 6y agoWe're approaching 3000 source files in our repo so I'm not sure. That is the issue.
- brundolf 6y agoHere's a question: are you using git, and is node_modules ignored? I ask because I think VSCode (by default) leans on the gitignore to decide which files to index. If it's indexing node_modules for whatever reason, that could create some serious overhead. https://www.reddit.com/r/vscode/comments/fpfnle/is_there_a_way_to_make_indexing_faster_for_large/ https://www.reddit.com/r/vscode/comments/fpfnle/is_there_a_w...
- ogre_codes 6y agonode_modules is in our .gitignore. I'm not sure I was super clear above, but I'm not too worried about fixing this. Now that I have a good VIM configuration I just don't feel the urge to go back.
- brundolf 6y agoThat's fair! Cheers
- ogre_codes 6y agoAlso, thanks for being rad! I do appreciate the suggestions!
- therealdrag0 6y agoDo you have tests and install any test plugins? I found out after a while my fan was blazing because a plug-in was auto running all the tests it could find in the background. Once I turned that off it’s been tolerable.