It does already do that

const logging = require('webpack/lib/logging/runtime');

logging.getLogger('test').info('helllo');

The above code outputs without color, do we have to specify some other configurations to get the colors?

@snitin315 strange, can you try to use warning/error?

Same behavior.

This is not how to use the webpack logger. Use compilation.getLogger("my-plugin")

we use logging before we run webpack and sometimes after, and when we do other actions that don't need webpack (like init/info/migrate/generate), so I think we can't use infrastructure logger.

@snitin315 we need to search way how we can implement colors using built-in logger

@sokra isn't it possible to have colors with runtime?

@snitin315 Please check the code, it is easy

The runtime logger is intended for in browser usage where the browser devtools take care of colors and filtering.

It's not intended for usage in node.js, because you won't have the ability to filter.

It probably makes sense to offer multiple different runtime loggers for web and node.js targets. A node.js logger could apply console colors and filter e. g. via env variable.

webpack would alias the logger depending on target.

As side effect you would be able to use the node.js runtime logger for your stuff too.

@sokra makes sense, How should I go ahead in Implementing this feature?

This issue had no activity for at least three months.

It's subject to automatic issue closing if there is no activity in the next 15 days.

Bump

Issue was closed because of inactivity.

If you think this is still a valid issue, please file a new issue with additional information.