Skip to content

Conversation

dankelleher
Copy link

This fixes an issue where any setting of the DEBUG env var would cause the library to log potentially sensitive information.

This clashes with the popular npm debug library which uses the same env var.

The solution introduces a namespace, that is compatible with that library. It also supports DEBUG=*.

Due to a recent security alert, the 'debug' package itself is not brought in as a dependency.

…e the library to log potentially sensitive information. This clashes with the popular npm debug library which uses the same env var. The solution introduces a namespace, that is compatible with that library. It also supports DEBUG=*. Due to a recent security alert, the 'debug' package itself is *not* brought in as a dependency.
@dankelleher
Copy link
Author

Fixes #32

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant