-
Notifications
You must be signed in to change notification settings - Fork 137
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
Reports all time as "building" when running npm start
#305
Comments
I have the same problem running my API ( |
I have the same problem. I use the built-in build task for watching my typescript file changes and waka time reports basically an infinite build time if I leave my vscode running in the background. Makes this extension worthless to me. Uninstalling until this issue is addressed. I'm actually surprised more people aren't reporting this. I would imagine that a large amount of projects use some kind of automated build/transpiling task. |
Would a config in your |
Possibly fixed with 02a4eaa. I'll comment here after the next plugin release when it's ready to test. |
Released with v24.0.0. |
I have a typical use-case for
npm start
- it runsvue-cli-service serve
which automatically rebuilds the project and serves it.This is an infinitely-running task. So it reports all the time as "building", which isn't correct. I write code, it re-compiles, I check the result, and go back to code.
I do realize that this plugin probably has no way of knowing if I'm waiting for build to finish or just running the server script.
Probably the easiest thing to do would be to check if the code editor is active and/or if the terminal is shown/hidden. However, these are pretty weak indicators...
The best solution would be to somehow integrate with
vue-cli-service
...For now, as a workaround, I'll probably resort to running
npm start
manually in the terminal instead of using npm scripts feature of VS Code.The text was updated successfully, but these errors were encountered: