Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

request: something like --watch mode #32

Open
dylang opened this issue Sep 19, 2022 · 0 comments
Open

request: something like --watch mode #32

dylang opened this issue Sep 19, 2022 · 0 comments

Comments

@dylang
Copy link
Contributor

dylang commented Sep 19, 2022

It would be helpful if there was something like --watch mode, or documentation for how to do this.

Example workflow:

  1. We run analyze-trace ts-trace
  2. Oh look, a hot spot!
Analyzed /Users/dylang/project/packages/example/tsconfig.json (trace.65458-188.json)
Hot Spots
└─ Check file /Users/dylang/project/packages/example/slow-type-in-here.js (1739ms)
   └─ Check variable declaration from (line 57, char 7) to (line 62, char 2) (1441ms)
      └─ Check expression from (line 57, char 30) to (line 62, char 2) (1441ms)
         └─ Check expression from (line 57, char 30) to (line 57, char 52) (1438ms)
            └─ Compare types 13361 and 4729 (1249ms)

  1. We make a change to try to fix it, and hit save....

This is where this feature request starts.

  1. analyze-trace automatically runs again. Fewer files may need to be recompiled so analyze-trace is only showing results from those re-compiles. Feature Request
  2. The output from analyze-trace tells us how much faster or slower each change is compared to the previous run. Bonus Feature Request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant