microsoft/typescript-analyze-trace

Issues

• Change exit codes to be more CI friendly

  #39 opened 10 months ago by Jaspooky
  2

• Error reading types file: Cannot create a string longer than 0x1fffffe8 characters

  #9 opened a year ago by amcasey
  6

• feature request: Show source code in the output

  #34 opened 2 years ago by dylang
  3

• output can break if data is too big

  #33 opened 2 years ago by dylang
  7

• request: something like `--watch` mode

  #32 opened 2 years ago by dylang
  0

• Make README instructions more digestible

  #29 opened 2 years ago by DanielRosenwasser
  3

• Guidance on output redirection for Windows

  #31 opened 2 years ago by DanielRosenwasser
  0

• Feature: Support language service traces

  #16 opened 2 years ago by amcasey
  4

• Consider using another metric than time to check for hot spots

  #28 opened 2 years ago by julienfouilhe
  3

• Support JSON output

  #21 opened 2 years ago by Ikaer
  4

• Add baseline tests

  #27 opened 2 years ago by amcasey
  0

• Feature: Instant Events

  #1 opened 2 years ago by amcasey
  1

• Feature: Program Construction

  #2 opened 2 years ago by amcasey
  3

• Feature: Emit

  #3 opened 2 years ago by amcasey
  0

• State machine incorrectly treats division as the start of a regex

  #14 opened 2 years ago by amcasey
  2

• Customizable thresholds constants

  #8 opened 2 years ago by amcasey
  5

• Consider stopping at the last getVariancesWorker frame

  #5 opened 2 years ago by amcasey
  0

• Can normalize-positions exit early once all positions have been normalized?

  #4 opened 2 years ago by amcasey
  0