3.2.6

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

Patches

• fix: performance issue (f312a89) (#625)

4.1.0

Minor Changes

• migrate Makefile to npm scripts (4236585)
• feat: Return namespaces string when invoking disable() (7ef8b41)

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

4.0.1

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

4.0.0

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

Due to the delay in release and the number of changes made (including bumping dependencies in order to mitigate vulnerabilities), it is highly recommended maintainers update to the latest package version and test thoroughly.

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

---

Major Changes

• move to XO (closes #397): ba8a424
• 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
• 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

Credits

Huge thanks to @DanielRuf, @EirikBirkeland, @KyleStay, @Qix-, @abenhamdine, @alexey-pelykh, @DiegoRBaquero, @febbraro, @kwolfy, and @TooTallNate for their help!

3.2.5

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.4

3.2.4 is DEPRECATED. See #603 (comment) for details.

This released fixed the missing files entry in package.json, mitigating the faulty 3.2.3 release.

3.2.3

3.2.3 is DEPRECATED. See #603 (comment) 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

3.2.2 is DEPRECATED. See #603 (comment) 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

3.2.1 is DEPRECATED. See #603 (comment) 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

3.2.0 is DEPRECATED. See #603 (comment) 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.