5.x Roadmap

[Qix-]

5.x Roadmap

It's about time for another step in bringing debug up to date - the 5.x major release.

I know it hasn't been a long time since 4.x was released, and I'm aware that its release kind of forced.. pushed.. nudged users to update their best practices.

Here's what to expect from the 5.x release:

• Custom output format (Customizing output format #582, Custom output formatting #645)
• Pluggable logging handlers ([RFC] Pluggable log handler #556)
• Timed sections (Add timed sections #485)
• No more transpiling (smaller package size) (Remove build step / bundling / babelifying #652, Remove build system #655)
• Patching of old debug versions for formatting and pluggability upgrades ([RFC] Compatibility layer #644)
• Overhaul of .enable() (debug.enable() flushes enabled namespaces #425, Wildcard in name doesn't auto enable on web #636, Regex injection in enable(namespaces) #737)
• Use console.debug() in the browser where available (Use console.debug() instead of console.log() where available (e.g. browsers) #600)
• Simpler documentation (Clean up README #649)
• Passing a function to avoid execution if namespace is disabled (Allow function to be passed & executed if enabled #497)
• Simplified codebase (lots dead code/dotfile removal; [RFC] Remove examples/ folder in lieu of proper README documentation? #650)
• Specify namespace in URL (Specify namespace with url in ESM #948)
• Several bugfixes

[OllieJennings]

Any chance we can get the issue fixed where you have

.env

DEBUG=*

And you run babel-node -r dotenv/config ./index.js

As right now this won't work

[Qix-]

@OllieJennings #705 please search next time.

[botond-veress]

@OllieJennings, that issue was closed prematurely, but it is not fixed. I switched back to debug@3 until the issue will get some attention and will be fixed. I suggest you to do the same thing.

[Qix-]

Please, there's no reason to post in two separate places about a closed ticket. Keep all discussion about that there - posting on the roadmap issue isn't going to get my attention any faster, I look at all issues regardless of urgency.

[getsnoopy]

Just to confirm, the 5.x roadmap stipulates that the module will use console.debug for Node.js environments as well, correct? The description in the OP here is different than that of the linked issue.

[Qix-]

@getsnoopy It'll be configurable. If you want to use something other than console.debug you would make your own log handler. That's defined in #556.

[suiyun39]

If remove build system, How to also supports esm and cjs module?
When used in nodejs, in most cases no bundle tools, requires the library to provide two versions of the export.

like this:

"exports": {
  ".": {
    "import": "./dist/my-lib.mjs",
    "require": "./dist/my-lib.umd.js"
  }
}