fix: getLogger not defined in child loader

[benjamin-hodgson]

This PR fixes #10 and #185.

This PR contains a:

• bugfix
• new feature
• code refactor
• test update
• typo fix
• metadata update

Motivation / Use-Case

Currently thread-loader is not compatible with less-loader, as outlined in #10 which was closed without resolution.

less-loader calls this.getLogger, which worker.js hadn't defined when calling loaderRunner.runLoaders, so it crashed. I set up getLogger to simply write to the child process's console, instead of messaging back to the parent process - the PoolWorker doesn't currently have access to the parent loader's getLogger function and it seemed like too big of a change to pass it in. I'm open to changing this (but would prefer to get this fix released as soon as possible since it's a live issue.)

Thanks!

Breaking Changes

None

Additional Info

[benjamin-hodgson]

Hello, just following up on this bugfix. This is a live issue affecting any build configurations using thread-loader with less-loader. Thanks!

[alexander-akait]

Ideally we should run webpack logger here, otherwise options from configuration for logging will not work

[benjamin-hodgson]

ce90da5

[alexander-akait]

Can we map methods created logger, we can have more them error/warn/log/debug

[allejo]

Just bumping this PR for some clarification.

Can we map methods created logger, we can have more them error/warn/log/debug

@alexander-akait Do you mean to just loop through the list of methods instead of manually specifying them? e.g.

const methods = ['error', 'warn', 'log', 'debug']];
const logger = {}

for (const key of methods ) {
    logger[key] = ...
}

return logger;

[allejo]

@alexander-akait Nudging this PR to see what's blocking it?

[abalbanyan]

@alexander-akait Would really appreciate a resolution to this. It's blocking my team from upgrading less-loader.