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 was archived by the owner on Jul 19, 2019. It is now read-only.
Since the TSU blueprints currently get compiled when you start the editor it can bump up the startup time for the editor quite a bit. There should ideally not be any reason at all to parse the TypeScript since it should all be baked into the .uasset.
The only thing I could see being a problem is if the generated typings were to change, in which case the TypeScript code should be reparsed and produce an error if faulty.
If recompiling on startup turns out to be unavoidable there's also the new .tsbuildinfo stuff that was released with TypeScript 3.4, which should cut the initial compile times down significantly.
Since the TSU blueprints currently get compiled when you start the editor it can bump up the startup time for the editor quite a bit. There should ideally not be any reason at all to parse the TypeScript since it should all be baked into the
.uasset.The only thing I could see being a problem is if the generated typings were to change, in which case the TypeScript code should be reparsed and produce an error if faulty.
If recompiling on startup turns out to be unavoidable there's also the new
.tsbuildinfostuff that was released with TypeScript 3.4, which should cut the initial compile times down significantly.