fix: Logger has not export in entry file

[taozi0818]

Fix #1275

[lamweili]

History in 2.0.0

It was changed from interface to class back in a1e40c2 which was released as 2.9.0.
It was probably due to the exposure of Logger as a global variable on configure().

log4js-node/lib/log4js.js

Line 208 in a1e40c2

Logger = loggerModule.Logger;

log4js-node/lib/logger.js

Lines 134 to 137 in a1e40c2

	return {
	LoggingEvent: LoggingEvent,
	Logger: Logger
	};

Refactored in 3.0.0

The global variable Logger has since been removed in 8084e80 which was released as 3.0.0.
But there was no change to the typings log4js.d.ts.

---

Thus, would a single line change from class to interface in log4js.d.ts (a reversal of a1e40c2) be better?

log4js-node/types/log4js.d.ts

Line 405 in 3582a00

export class Logger {

-        export class Logger { 
+        export interface Logger { 

Because Logger should not be used standalone nor exposed. It won't work if log4js is not configured (which is also handled silently by getLogger()).

It is wrapped around and should only be retrieved from getLogger().

log4js-node/lib/log4js.js

Lines 144 to 154 in 3582a00

	function getLogger(category) {
	if (!enabled) {
	configure(
	process.env.LOG4JS_CONFIG || {
	appenders: { out: { type: 'stdout' } },
	categories: { default: { appenders: ['out'], level: 'OFF' } },
	}
	);
	}
	return new Logger(category || 'default');
	}

[taozi0818]

OK. Both methods are available. The key point is keeping them consistent.

[lamweili]

@taozi0818 Thanks! I rebased.