Currently rulus-loader offers insight into your component hierarchy via messages logged into the webpack loader pipeline. Their use is to relay information relating to missing required and optional component files eg. index.js, index.html, test.js, etc. These messages are currently static, and while beneficial in the majority case, can produce a lot of noise especially as your project grows. For more advanced Rukus apps ideally we should offer a way to configure these messages.
My thoughts are toward adding a logLevel configuration option that can be passed to the loader.
rukus-loader?["./components"]&logLevel=verbose
where the available logLevel options are:
verbose
Everything from errors, with additional messages based on missing test.js files in normal mode, and missing styles.css in css-modules mode.
errors
Only log messages relating to missing required component files index.js and index.html.
none
Off, probably not a good idea.
@obrin I'd be interested to hear your thoughts toward this, given your interest in the topic of Rukus loader output. :smile:
Currently
rulus-loaderoffers insight into your component hierarchy via messages logged into the webpack loader pipeline. Their use is to relay information relating to missing required and optional component files eg. index.js, index.html, test.js, etc. These messages are currently static, and while beneficial in the majority case, can produce a lot of noise especially as your project grows. For more advanced Rukus apps ideally we should offer a way to configure these messages.My thoughts are toward adding a
logLevelconfiguration option that can be passed to the loader.rukus-loader?["./components"]&logLevel=verbosewhere the available
logLeveloptions are:test.jsfiles in normal mode, and missingstyles.cssin css-modules mode.index.jsandindex.html.@obrin I'd be interested to hear your thoughts toward this, given your interest in the topic of Rukus loader output. :smile:
Ref: #8