Document output of --generateTrace about typescript-wiki HOT 4 CLOSED

Until you get a more definitive answer: I'm pretty sure we try to conform to that format in tracing, with. respect to the types - the code which generates the types is short and readable, it would beat my explanation, it's this file: https://github.com/microsoft/TypeScript/blob/db9e007900238f12afc7a231817cee1b087b037d/src/compiler/tracing.ts

from typescript-wiki.

Thanks for your interest! One small caveat: this functionality isn't mature enough that we're ready to guarantee changes will be backwards compatible. Obviously, that will be a consideration, since our own tooling needs to continue to work with older TS versions, but it shouldn't be regarded as a contract.

cc @jakebailey who's also thinking about perf tooling.

from typescript-wiki.

@amcasey thanks for clarifying. I'm all for supporting that format due to it's wide usage and support from existing tools, but I understand if it might not make sense for you at some point. If I may suggest one point worth addressing if you decide to change this format is possibly having types.json somehow included into the trace. I think this would unlock some nice workflow improvements. The problem I've had so far is that --generateTrace gives very meaningful output in detecting files that cause problems, but drilling down to the types is very brittle (your pkg is very helpful for that btw).
I may take a stab at this myself with our flamegraph when I have some time and report back.
Thanks for all the answers everyone!

from typescript-wiki.

Thank you for the reply @orta, I think that suffices for now. I'll close the issue, thanks again!

from typescript-wiki.