debug

Fixes (hopefully) the inefficient regex warnings in .enable().

Minor version as this is invariably going to break certain users who misuse the .enable() API and expected it to work with regexes, which was never supported nor documented. That's on you, sorry - that functionality won't be added back.

Patch Release 4.3.3

This is a documentation-only release. Further, the repository was transferred. Please see notes below.

• Migrates repository from github.com/visionmedia/debug to github.com/debug-js/debug. Please see notes below as to why this change was made.

• Updates repository maintainership information

• Updates the copyright (no license terms change has been made)

• Removes accidental epizeuxis

• Adds README section regarding usage in child procs

Repository Migration Information

I've formatted this as a FAQ, please feel free to open an issue for any additional question and I'll add the response here.

Q: What impact will this have on me?

In most cases, you shouldn't notice any change.

The only exception I can think of is if you pull code directly from github.com/visionmedia/debug, e.g. via a "debug": "visionmedia/debug"-type version entry in your package.json - in which case, you should still be fine due to the automatic redirection Github sets up, but you should also update any references as soon as possible.

Q: What are the security implications of this change?

If you pull code directly from the old URL, you should update the URL to github.com/debug-js/debug as soon as possible. The old organization has many approved owners and thus a new repository could (in theory) be created at the old URL, circumventing Github's automatic redirect that is in place now and serving malicious code. I (@qix-) also wouldn't have access to that repository, so while I don't think it would happen, it's still something to consider.

Even in such a case, however, the officially released package on npm (debug) would not be affected. That package is still very much under control (even more than it used to be).

Q: What should I do if I encounter an issue related to the migration?

Search the issues first to see if someone has already reported it, and then open a new issue if someone has not.

Q: Why was this done as a 'patch' release? Isn't this breaking?

No, it shouldn't be breaking. The package on npm shouldn't be affected (aside from this patch release) and any references to the old repository should automatically redirect.

Thus, according to all of the "APIs" (loosely put) involved, nothing should have broken.

I understand there are a lot of edge cases so please open issues as needed so I can assist in any way necessary.

Q: Why was the repository transferred?

I'll just list them off in no particular order.

• The old organization was defunct and abandoned.

• I was not an owner of the old organization and thus could not ban the non-trivial amount of spam users or the few truly abusive users from the org. This hindered my ability to properly maintain this package.

• The debug ecosystem intends to grow beyond a single package, and since new packages could not be created in the old org (nor did it make sense for them to live there), a new org made the most sense - especially from a security point of view.

• The old org has way, way too many approved members with push access, for which there was nothing I could do. This presented a pretty sizable security risk given that many packages in recent years have fallen victim to backdoors and the like due to lax security access.

Q: Was this approved?

Yes.[archive]

Q: Do I need to worry about another migration sometime in the future?

No.

Minor Release

• Replaced phantomJS with chrome backend for browser tests

• Deprecated and later removed Changelog.md in lieu of releases page

• Removed bower.json

• Removed .eslintrc (since we've switched to XO)

• Removed .coveralls.yml

• Removed the build system that was in place for various alternate package managers

• Removed the examples folder

• Switched to console.debug in the browser only when it is available

• Copied custom logger to namespace extension

• Added issue and pull request templates

• Added "engines" key to package.json

• Added ability to control selectColor

• Marked supports-color as an optional peer dependency

This backport fixes a bug in coveralls configuration as well as the .extend() function.

Patches

• Copy custom logger to namespace extension (#646, 57ef085)

Minor Changes

• Migrate Makefile to npm scripts

• Return namespaces string when invoking disable()

Massive thank you to @mblarsen and @outsideris for knocking out two long-awaited changes.

This patch restores browserify functionality as well as keeping the intended functionality with Unpkg.com.

Patches

• Fix browserify and supply alternative unpkg entry point (closes #606): 99c95e3

A long-awaited release to debug is available now: 4.0.0.

This release drops support for Node 4 and 5 in alignment with the Node.js LTS Release Schedule.

Major Changes

• breaking

  Move to XO (closes #397): ba8a424

• breaking

  Add Node.js 10, remove Node.js 4 (#583): 05b0ceb

Minor Changes

• Bump vulnerable packages: 853853f

• Fix nwjs support (#569): 207a6a2

• Add instance extends feature (#524): e43e5fe

• Add TVMLKit support (#579): 02b9ea9

Patches

• Clean up builds: 3ca2331

• removed

  Remove needless command aliases in makefile: 9f4f8f5

• No longer checking for BROWSER=1: 623c08e

• Fix tests: 57cde56

• Clean up makefile: 62822f1

• Fix tests: 833b6f8

• Add .editorconfig: 2d2509e

• Add yarn-error.log to .gitignore: 7e1d5d9

• Improve usability of Windows notes w/ examples for prompts & npm script (#577): 1ad1e4a

• Drop usage of chrome.storage (or make the storage backend pluggable): 71d2aa7

• Detect 'process' package: 225c66f

• Update ms to 2.1.1 (#539): 22f9932

• Update .npmignore (#527): a5ca7a2

• Fix colors with supports-color@5: 285dfe1

• Document enable() (#517): ab5083f

• Refactor to make the common code be a setup function (#507): 7116906

• Simplify and improve: da51af8

• Use babel-ified distributed source for browsers: b3f8f8e

This backport fixes a 4x performance regression when debug is disabled.

Patches

• Performance issue

This patch restores browserify functionality as well as keeping the intended functionality with Unpkg.com.

It is a backport of the 4.0.1 release.

Patches

• Fix browserify and supply alternative unpkg entry point (closes #606): cc5f146

3.2.3 is DEPRECATED. See #603 for details.

This release mitigated the breaking changes introduced in 3.2.0 where ./node.js was removed, breaking a very select few users on older releases of babel-core, as well as users that used an undocumented require('debug/node').

./node.js was temporarily added to the repository at this time; however, this release failed to include node.js in the files key in package.json and thus didn't fix the issue. 3.2.4 rectified this issue.

3.2.2 is DEPRECATED. See #603 for details.

This release mitigated the breaking changes introduced in 3.2.0 where ES6 features were being used on users of Node 4, causing crashes upon inclusion.

It employed a temporary Babel pass on the entire codebase in lieu of a hard reversion (so this version is, effectively, a backport of the fixes and features ultimately introduced in 4.0.0).

3.2.1 is DEPRECATED. See #603 for details.

This release, along with 3.2.0, were subsequently released together as 4.0.0 (a major bump). You can review the complete changes in that release's details.

A quick hotfix to address Browser builds - debug is now compiled down to IE8-compatible code via Babel upon release.

CDNs that honor the "browser": key in package.json should now reflect these changes (previously, they would serve the non-bundled ES6 version).

Patches

• Use babel-ified distributed source for browsers: b3f8f8e

3.2.0 is DEPRECATED. See #603 for details.

This release was intended to be the next release of Debug but introduced breaking changes that were overlooked at the time of release. As such it has been deprecated on npm and should not be used.

This release, along with 3.2.1, were subsequently released together as 4.0.0 (a major bump). You can review the included changes in that release's details.

Minor Changes

• Ignore package-lock.json: e7e568a

• removed

  Remove component.json: 47747f3

• removed

  Remove "component" from package.json: bdb7e01

• Add DEBUG_HIDE_DATE env var

Patches

• Fix browser detection: fdfa0f5

• security

  Remove ReDoS regexp in %o formatter

Featuring pretty new colors!

Major Changes

• breaking

  Remove DEBUG_FD

• breaking

  Make millisecond timer namespace specific and allow 'always enabled' output

• breaking

  Use Date#toISOString() instead to Date#toUTCString() when output is not a TTY

• breaking

  enabled() updates existing debug instances

Minor Changes

• Add destroy() function

• Document enabled flag

• Support 256 colors

• Update "browserify" to v14.4.0: 826fd94

• Separate Node.js and web browser examples: 87880f6

• More readme screenshots replaced: 25eb545

• Add Namespace Colors section to readme: 8b5c438

• Separate the Node and Browser tests in Travis: f178d86

Patches

• Component: Update "ms" to v2.0.0: d2dd80a