You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 16, 2020. It is now read-only.
The server works fine once it's started and it has warmed up... however, that warmup takes from 20-30 seconds here... I get some "Found package file://..." messages from the server, and then it loads plugins and after that it all starts working.
Is there a way we can accelerate that "warmup" process? as I don't have completions or hover information until it ends "finding packages". Maybe those found packages could be cached and then do another "find" in the background afterwards when the server is already working for the client?
The text was updated successfully, but these errors were encountered:
This issue is caused by the server scanning all files in the rootUri and only making them available to the Typescript back-end after the file has been scanned. The root cause is the same as for this issue: #471
The server works fine once it's started and it has warmed up... however, that warmup takes from 20-30 seconds here... I get some "Found package file://..." messages from the server, and then it loads plugins and after that it all starts working.
Is there a way we can accelerate that "warmup" process? as I don't have completions or hover information until it ends "finding packages". Maybe those found packages could be cached and then do another "find" in the background afterwards when the server is already working for the client?
The text was updated successfully, but these errors were encountered: