A Node.js module for sending events to Honeycomb, a service for debugging your software in production. For tracing support and automatic instrumentation of Express and other common libraries, check out our Beeline for NodeJS.
NOTE For use in browser-side JavaScript applications, generate an API key that has permission only to send events.
Node 14.18+
See DEVELOPMENT.md
Features, bug fixes and other changes to libhoney are gladly accepted. Please open issues or a pull request with your change.
All contributions will be released under the Apache License 2.0.
Use npm version --no-git-tag-version to update the version number using major, minor, patch, or the prerelease variants premajor, preminor, or prepatch. We use --no-git-tag-version to avoid automatically tagging - tagging with the version automatically triggers a CI run that publishes, and we only want to do that upon merging the PR into main.
After doing this, follow our usual instructions for the actual process of tagging and releasing the package.
FAQs
Honeycomb.io Javascript library
The npm package libhoney receives a total of 33,794 weekly downloads. As such, libhoney popularity was classified as popular.
We found that libhoney demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 19 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.
