Evgeniy Pavlov

Implementing the support of browsers from the Stone Age, you risk yourself stuck in the Stone Age. If this is your choice, then I'm not going to challenge it. But...

> I think IE 11 is a good & low bar nowadays, and I'm fine with only publishing a 'modern' build that supports IE11+. It sounds delicious. My current implementation...

@pimterry I made this lock because the child logger can not override the plugin in the parent logger when assigning the plugin. This leads to the fact that if the...

In the current implementation, loglevel, originalFactory and pluginFactory are static because I allow the plugin to be applied exclusively to the root logger. I can easily rewrite the code so...

https://github.com/kutuluk/loglevel-plugin-prefix/commit/c7c974998eb2929c0e410e7bbbaeec3c30d3e1a6 Solved =)

> Wrap the methods only if it was applied directly to a child, or its been inherited from the root, not applied (i.e. it's running on a named child logger,...

Simplified plugin: ```javascript const defaults = { prefix: 'prefix', }; const configs = {}; const apply = (logger, config) => { if (!logger || !logger.setLevel) { throw new TypeError('Argument is...