Allow specifying tsserver NODE_ENV --max-old-space-size via config variable #320
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
When working on larger projects, I noticed that using various commands (e.g. jump to definition, show hint) would make vim hang for a long time. With some hacking, I realized that bumping the --max-old-space-size of the node process running tsserver seemed to help with this. We expose config variable `tsuquyomi_tsserver_max_old_space_size` to allow the user to easily configure the heap size for the node process running tsserver.
seankwalker
changed the title
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.
Hey there, longtime tsuquyomi user here! Thank you for such a wonderful plugin 🙏 When working on larger projects, I noticed that using various commands (e.g. jump to definition, show hint) would make vim hang for a long time, with tsserver evidently struggling. With some hacking, I realized that bumping the
--max-old-space-sizeof the node process running tsserver seemed to help with this.This PR exposes config variable
tsuquyomi_tsserver_max_old_space_sizeto allow the user to easily configure the heap size for the node process running tsserver.There's no open issues for this or anything, but it's helped save me some time so figured I'd open a PR to see if there's any interest in getting this in mainline. Thanks!
** the Japanese in the docs was translated by GPT-4o so please forgive any mistakes