Closed kuba-orlik closed 8 years ago
@kuba-orlik your changes doesn't work. We don't have information about plugin name. I've checked 'origin/issue#259_correct_plugin_manager_output' branch. (sealious 0.6.23)
23:52:45.539 - info: Loading plugins...
23:52:45.558 - debug: sealious (/home/arkadiusz/Projects/Sealious/sealious/package.json) requires: sealious-datastore-tingo
23:52:45.638 - info: ✓ ${plugin_name}
23:52:45.640 - debug: hello-world (/home/arkadiusz/Projects/Sealious/hello-world/package.json) requires: sealious-channel-rest
23:52:45.641 - debug: sealious-channel-rest (/home/arkadiusz/Projects/Sealious/hello-world/node_modules/sealious-channel-rest/package.json) requires: sealious-www-server
23:52:46.078 - info: ✓ ${plugin_name}
23:52:46.081 - info: ✓ ${plugin_name}
I've used the
resolve
package to make the PluginManager behave correctly when used on an app withnpm link
-ed Sealious plugins.Now the PluginManager's output is separated into
info
anddebug
messages, to make them more readable.PluginManager's output before this commit:
After, Logger set up to
debug
level:And after with
info
debug level: