debug
ironNode
Our great sponsors
| debug | ironNode | |
|---|---|---|
| 26 | - | |
| 10,994 | 2,333 | |
| 0.4% | - | |
| 3.6 | 0.0 | |
| 7 months ago | over 1 year ago | |
| JavaScript | JavaScript | |
| MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
debug
-
Conditional logging
Another way to solve this is to have the logs in place, but only enable them conditionally. If you enable all the logs are the time, you only get a lot of noise that won't help you. If you are using JavaScript, you can use the package debug to add logs that are active by the DEBUG environment variable.
-
Has anyone figured out how to enable the millisecond diff feature in the debug package?
I'm using the debug package: https://www.npmjs.com/package/debug, but some reason I don't see millisecond diffs, which would be really useful.
- Help I have a JavaScript Lib that blows away competition but nobody knows of it
-
What is the DEBUG 🐛 environment variable in Node.js, and how to use it?
Although it's used by Express, it's indeed more broadly, the way a popular NPM package called debug works, which is used internally in Express too. Under the hood, the debug package expects the DEBUG environment variable to determine what debug messages to print (could be on the console, or into a file, or into stdout to be collected by a log aggregator service).
-
Automating console logs for dev but removing for prod?
Finally, if they're logs you want to be able to inspect in production without printing them to the console by default, you can use debug.
-
After having used many loggers/debuggers...
It is a drop-in, TypeScript replacement to enhance the widely popular https://www.npmjs.com/package/debug (230k weekly downloads).
-
Create a Node.js command-line library with NRWL NX workspace
debug - npm - Required. A popular library to write debug logs.
-
Debugging Figma and other packaged Electron apps in Visual Studio Code
I strongly recommend using the debug package from NPM to organize your log messages
-
Is it bad practice to log within a shared library?
Use the [debug npm library](https://www.npmjs.com/package/debug) to disable your logging unless someone provides the right environment variable (e.g. DEBUG=* which enables all logging)
-
Debug build vs Prod build
A lot of tools rely on the NODE_ENV environment variable for that, React included. Another great package that’s pretty popular is https://www.npmjs.com/package/debug You can create namespaces and then filter the logs you are interested in.
ironNode
We haven't tracked posts mentioning ironNode yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
node-inspector - Node.js debugger based on Blink Developer Tools
swagger-stats - API Observability. Trace API calls and Monitor API performance, health and usage statistics in Node.js Microservices.
npm-fast-installer - npm-fast-installer - NPM install configuration in top of YAML for fast NPM install usage.
TraceGL - TraceGL MPL release
bugger - Bugs bugging you? Bug back.
devtool - [OBSOLETE] runs Node.js programs through Chromium DevTools
ndb - ndb is an improved debugging experience for Node.js, enabled by Chrome DevTools
0x - 🔥 single-command flamegraph profiling 🔥
longjohn - Long stack traces for node.js inspired by https://github.com/tlrobinson/long-stack-traces
leakage - 🐛 Memory leak testing for node.
why-is-node-running - Node is running but you don't know why? why-is-node-running is here to help you.