Replace winston deep import with main-entry import for ESM

[cuzzlor]

Summary

Fixes a runtime SyntaxError in the v2 beta ESM build when consumers import from @makerx/node-winston under pure ESM (e.g. Vitest, Node 22+ with "type": "module"):

SyntaxError: The requested module 'winston/lib/winston/transports' does not provide an export named 'Console'

The offending line was:

import { Console, ConsoleTransportOptions } from 'winston/lib/winston/transports'

That worked under CJS require() but breaks in ESM for two reasons (verified against winston 3.19.0):

1. Directory import. Node ESM requires the explicit /index.js suffix; otherwise it throws ERR_UNSUPPORTED_DIR_IMPORT.
2. Lazy-getter named exports aren't statically detectable. Even with the suffix, winston/lib/winston/transports/index.js defines Console via Object.defineProperty(exports, 'Console', { get() { return require('./console') } }). cjs-module-lexer (what Node's ESM→CJS interop uses) doesn't expose this shape as an ESM named binding, so import { Console } fails.

Fix: go through winston's main entry, which does exports.transports = require('./winston/transports') — a form cjs-module-lexer handles cleanly. ConsoleTransportOptions is now sourced via the transports namespace (type-only).

Also updated the direct-usage example in the README to match.

Test plan

• npm run check-types passes
• npm run lint passes
• npm run test — all 34 tests pass
• npm run build — verified dist/index.mjs no longer references winston/lib/winston/transports
• Swapped the built package into a consumer ESM project (vitest) — the original SyntaxError: Named export 'Console' not found is gone and the suite passes

🤖 Generated with Claude Code