search

vigetlabs / blendid

A delicious blend of gulp tasks combined into a configurable asset pipeline and static site builder
MIT License
4.97k stars 683 forks source link

Possible to log webpack before browsersync? #529

Open olets opened 6 years ago

olets commented 6 years ago

Haven't looked into whether this is feasible, but from a user's point of view it would be helpful to have the initial logging of yarn run blendid read

yarn run blendid
[…]
Finished 'default' after […] s
webpack built 0a5c84e7fc9c707f5524 in 5949ms

webpack: Compiled successfully.
[Browsersync] Proxying: http://myfreetaxes.test
[Browsersync] Access URLs:
 ------------------------------------
       Local: http://localhost:3000
    External: http://192.168.0.6:3000
 ------------------------------------
          UI: http://localhost:3001
 UI External: http://192.168.0.6:3001
 ------------------------------------
[Browsersync] Watching files...

Currently, the Browsersync logs come before the webpack logs.

yarn run blendid
[…]
Finished 'default' after […] s
[Browsersync] Proxying: http://myfreetaxes.test
[Browsersync] Access URLs:
 ------------------------------------
       Local: http://localhost:3000
    External: http://192.168.0.6:3000
 ------------------------------------
          UI: http://localhost:3001
 UI External: http://192.168.0.6:3001
 ------------------------------------
[Browsersync] Watching files...
webpack built 0a5c84e7fc9c707f5524 in 5949ms

webpack: Compiled successfully.

The effect is that a new user can run yarn run blendid, see "webpack: Compiled successfully.", miss the fact that "[Browsersync] Watching files..." still applies, and wonder what's going on.

In combination with #528, it's possible to accidentally run yarn run blendid --build (instead of yarn run blendid -- build), see that webpack compiled successfully, and wonder why the command hasn't completed.