-
Notifications
You must be signed in to change notification settings - Fork 930
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
Improved output for the bit watch
command
#1634
Comments
I totally agree with you on this one. I think that the baseline for a proper
|
@itaymendel I don't see why bit/node version are necessary for the output.
about after the build process, I'm not sure if we want to aggregate errors or just show the first we got. |
The main reason I want versions and stuff is that usually, this command runs from another terminal, and perhaps... for some reason there's an env-var that made the version different for node or bit. As for aggregate errors or not - I still haven't decided on how the output is structured. Trying to figure out what makes sense as an output for the command. Then we'll decide on the how it is presented :) |
Yes I can understand that. No problem, we can make it. |
bit binary version: <version>
node version: <version>
started watching for component changes to rebuild
running build for <component id>
<path to dist>.js
<path to dist>.js
running build for <component id>
<path to dist>.js |
@itaymendel We currently have a --verbose flag, we use for output all the files we watch. |
The output has been improved by the commit above. PR #1846. |
Description
when running bit watch on an imported component, the output isn't clear. see screenshot.
Expected Behavior
I think there should be better separation between component name and files in that component
Actual Behavior
Steps to Reproduce the Problem
Specifications
The text was updated successfully, but these errors were encountered: