Package incompatibility with Bun runtime and Docker

[Jajared]

Description

When using debug-next (v0.3.0) with Bun runtime (v1.1.30), logging functionality doesn't work as expected. The logger initialization works in the main application file but fails to properly log in other modules/routes.

Environment

• Bun: 1.1.30
• debug-next: 0.3.0
• OS: Linux (Docker container, with docker compose)

Steps to Reproduce

1. Set up logger initialization in main app file:

import { LogBase } from 'debug-next'
LogBase.init('app-name', __dirname)

2. Try to use logging in route files:

import { Log } from 'debug-next'
const { log } = Log()
log('Test message') // This fails to output

Current Behavior

• Logging works in the main application file where LogBase is initialized
• Logging fails silently in other modules/route files
• No error messages are shown
• Environment variables (DEBUG=app-name:*) are properly set

Expected Behavior

• Logging should work consistently across all files
• File paths should be automatically resolved
• Namespace prefixing should work as documented

Attempted Solutions

1. Tried using different environment configurations:
   • Setting DEBUG and FORCE_COLOR environment variables
   • Using different log levels
2. Attempted to use ts-node-dev and nodemon as alternatives
3. Tried various logger initialization approaches

Impact

This issue prevents proper debugging and monitoring in production environments when using Bun as the runtime. Currently requires falling back to Node.js for development to maintain logging functionality.

Additional Context

The issue appears to be related to how Bun handles module resolution and global state management differently from Node.js. The logger initialization state is not properly shared across modules in the Bun environment.