When using browser-sync, which parched-tasks-webapps does, CSS is already hot-reloaded, and there's no worry of configuring different "loaders" for the case of

When using browser-sync, which parched-tasks-webapps does, CSS is already hot-reloaded, and there's no worry of configuring different "loaders" for the case of a javascript file on the server trying to require a CSS file. In both cases, the page is loading an external stylesheet, so both are as susceptible to FOUCs as the other. This is only my opinion, but using CSS loaders backs you into a corner where your javascript file is suddenly less portable, since the environment it will be running on needs to be aware of it.