We want to explore performance measurement APIs in js-debug. In this month, we plan to:

• Create a command that could be called by extension plugins to capture profiles

• Expose a way for users to capture and save profiles

  • Basic profiling support
  • Rich termination conditions Add termination condition for profiling #415
  • Paused and breakpoint state while profiling Tell vscode that the debugger has continued, and unverify breakpoints, while profiles run #416
  • 💪 Support for capturing heap and tracing-API-based profiles Support for capturing heap and tracing-API-based profiles #435
  • Open profiles in untitled editors on complete Open profiles in untitled editors on complete #432

• Investigation into visualization options for the profiles (tracked in April visualization work #434)

• Add an option to start the profiling before the program launches Add an option to start the profiling before the program launches #467