Debug Versions Save

A tiny JavaScript debugging utility modelled after Node.js core's debugging technique. Works in Node.js and web browsers

4.3.4

2 years ago

What's Changed

New Contributors

Full Changelog: https://github.com/debug-js/debug/compare/4.3.3...4.3.4

4.3.3

2 years ago

Patch Release 4.3.3

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

  • Migrates repository from https://github.com/visionmedia/debug to https://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 (#828)
  • Adds README section regarding usage in child procs (#850)

Thank you to @taylor1791 and @kristofkalocsai for their contributions.

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 https://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 https://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).

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.

4.3.2

3 years ago

Patch release 4.3.2

  • Caches enabled statuses on a per-logger basis to speed up .enabled checks (#799)

Thank you @omg!

4.3.1

3 years ago

Patch release 4.3.1

  • Fixes a ReDOS regression (#458) - see #797 for details.

4.3.0

3 years ago

Minor release

  • Deprecated debugInstance.destroy(). Future major versions will not have this method; please remove it from your codebases as it currently does nothing.
  • Fixed quoted percent sign
  • Fixed memory leak within debug instances that are created dynamically

4.2.0

3 years ago

Minor Release

  • Replaced phantomJS with chrome backend for browser tests
  • Deprecated and later removed Changelog.md in lieu of releases page
  • Removed bower.json (#602)
  • 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 (#650)
  • Switched to console.debug in the browser only when it is available (#600)
  • Copied custom logger to namespace extension (#646)
  • Added issue and pull request templates
  • Added "engines" key to package.json
  • Added ability to control selectColor (#747)
  • Updated dependencies
  • Marked supports-color as an optional peer dependency

4.1.1

5 years ago

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

Patches

  • test: only run coveralls on travis (#663, #664, d0e498f159bd425b3403db38c98fe26a345d4dcd)
  • copy custom logger to namespace extension (#646, 57ef085703a0158679cc4a56a4980653b828ce51)

3.2.6

5 years ago

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

Patches

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

4.1.0

5 years ago

Minor Changes

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

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

4.0.1

5 years ago

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): 99c95e3d54b07a918ad65bc148a2930ea8bfdd02