loggin-js VS debug

Compare loggin-js vs debug and see what are their differences.

debug

A tiny JavaScript debugging utility modelled after Node.js core's debugging technique. Works in Node.js and web browsers (by debug-js)
Our great sponsors
  • Appwrite - The Open Source Firebase alternative introduces iOS support
  • Scout APM - Less time debugging, more time building
  • SonarLint - Deliver Cleaner and Safer Code - Right in Your IDE of Choice!
loggin-js debug
0 14
20 10,142
- 0.7%
1.1 4.9
3 months ago 27 days ago
JavaScript JavaScript
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

loggin-js

Posts with mentions or reviews of loggin-js. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning loggin-js yet.
Tracking mentions began in Dec 2020.

debug

Posts with mentions or reviews of debug. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-02-03.
  • Ask HN: How do you deal with logging while developing a webapp?
    1 project | news.ycombinator.com | 17 May 2022
    I have a decently complex webapp I'm working on and have found logging to be a pain point. I'm currently using debug [1] and viewing the logs in the chrome dev tools console. The issue I've had is that the console gets too noisy and crowded with all logging turned on but if I'm more selective with logging, then I often regret not having logs when I run into a bug. It'd be ideal to have fairly verbose logging always on but be able to have good control over how the logs are filtered. The console log filtering functionality in chrome and Firefox seems pretty limited and I can't do basic filters like "component1Logs | component2Logs".

    I imagine there's some library I could use which runs a local server, logs to some local file, and allows me to filter the logs with whatever shell tools are best. I haven't been able to find such a tool though and also would miss having the object exploration abilities that are in the browser console.

    [1] https://www.npmjs.com/package/debug

  • Full Demo: A new kind of Debugger for JavaScript (Dbux, this time w/ examples)
    1 project | reddit.com/r/javascript | 22 Mar 2022
    Really verbose logging with flags when I want to inspect something. Flags might not be the right word, it's essentially contextual log levels with glob patterns like in debug
  • 003/100 Days of Code: Debugging Javascript
    1 project | dev.to | 19 Feb 2022
  • Stop using console.log! @lvkshLogger, your new favorite logging lib!
    2 projects | reddit.com/r/node | 3 Feb 2022
    i still prefer debug
  • Debug traces library in python ?
    2 projects | reddit.com/r/learnpython | 30 Dec 2021
    I`m searching for a library to put debug traces in your python code, similar to this node js library https://www.npmjs.com/package/debug
  • What’s the most underrated Developer Tools debugging Tip/Trick?
    2 projects | reddit.com/r/reactjs | 20 Dec 2021
    Use the debug library https://www.npmjs.com/package/debug
  • can't install ganashe through npm
    5 projects | reddit.com/r/Truffle | 13 Nov 2021
    npm install npm WARN old lockfile npm WARN old lockfile The package-lock.json file was created with an old version of npm, npm WARN old lockfile so supplemental metadata must be fetched from the registry. npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient... npm WARN old lockfile npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '[email protected]', npm WARN EBADENGINE required: { node: '12.13.1' }, npm WARN EBADENGINE current: { node: 'v16.11.1', npm: '8.1.3' } npm WARN EBADENGINE } npm WARN deprecated [email protected]: Renamed to @metamask/safe-event-emitter npm WARN deprecated [email protected]: Please update to ini >=1.3.6 to avoid a prototype pollution issue npm WARN deprecated [email protected]: This package is broken and no longer maintained. 'mkdirp' itself supports promises now, please switch to that. npm WARN deprecated [email protected]: flatten is deprecated in favor of utility frameworks such as lodash. npm WARN deprecated [email protected]: This package is broken and no longer maintained. 'mkdirp' itself supports promises now, please switch to that. npm WARN deprecated [email protected]: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated [email protected]: this library is no longer supported npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated [email protected]: this library is no longer supported npm WARN deprecated @web3-js/[email protected]: This package is deprecated, for a pure JS implementation please use scrypt-js npm WARN deprecated [email protected]: Deprecated in favor of '@metamask/eth-sig-util' npm WARN deprecated [email protected]: Please use Util.Account class found on package [email protected]^7.0.6 https://github.com/ethereumjs/ethereumjs-util/releases/tag/v7.0.6 npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated npm WARN deprecated [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools. npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated npm WARN deprecated [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools. npm WARN deprecated [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools. npm WARN deprecated [email protected]: use String.prototype.padStart() npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/block. Please update. npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/block. Please update. npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/block. Please update. npm WARN deprecated [email protected]: Deprecated in favor of '@metamask/eth-sig-util' npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/block. Please update. npm WARN deprecated [email protected]: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies. npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies. npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated [email protected]: We don't use this library anymore so you shouldn't either. Use e.g. 'uuid' instead! npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/tx. Please update. npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/tx. Please update. npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/tx. Please update. npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/tx. Please update. npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/tx. Please update. npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated [email protected]: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates. npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/ethash. Please update. npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated [email protected]: This module has been superseded by the multiformats module npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.) npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/blockchain. Please update. npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/tx. Please update. npm WARN deprecated [email protected]: This module has been superseded by the multiformats module npm WARN deprecated [email protected]: This module has been superseded by the multiformats module npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/tx. Please update. npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/tx. Please update. npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/tx. Please update. npm WARN deprecated [email protected]: This module has been superseded by the multiformats module npm WARN deprecated @web3-js/[email protected]: The branch for this fork was merged upstream, please update your package to [email protected] npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/vm. Please update. npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/vm. Please update. npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/vm. Please update. npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/block. Please update. npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/block. Please update. npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/block. Please update. npm WARN deprecated [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x. npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/common. Please update. npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/common. Please update. npm WARN deprecated [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x. npm WARN deprecated [email protected]: New package name format for new versions: @ethereumjs/vm. Please update. npm WARN deprecated [email protected]: This module has been superseded by the multiformats module npm WARN deprecated [email protected]: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap. npm WARN deprecated [email protected]: Version no longer supported. Upgrade to @latest npm WARN deprecated [email protected]: [email protected]<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js. npm WARN deprecated [email protected]: [email protected]<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js. npm WARN deprecated [email protected]: [email protected]<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js. npm ERR! code 1 npm ERR! path /home/mehdielghali/Desktop/ganache-ui/node_modules/node-sass npm ERR! command failed npm ERR! command sh -c node scripts/build.js npm ERR! Building: /usr/bin/node /home/mehdielghali/Desktop/ganache-ui/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library= npm ERR! gyp info it worked if it ends with ok npm ERR! gyp verb cli [ npm ERR! gyp verb cli '/usr/bin/node', npm ERR! gyp verb cli '/home/mehdielghali/Desktop/ganache-ui/node_modules/node-gyp/bin/node-gyp.js', npm ERR! gyp verb cli 'rebuild', npm ERR! gyp verb cli '--verbose', npm ERR! gyp verb cli '--libsass_ext=', npm ERR! gyp verb cli '--libsass_cflags=', npm ERR! gyp verb cli '--libsass_ldflags=', npm ERR! gyp verb cli '--libsass_library=' npm ERR! gyp verb cli ] npm ERR! gyp info using [email protected] npm ERR! gyp info using [email protected] | linux | x64 npm ERR! gyp verb command rebuild [] npm ERR! gyp verb command clean [] npm ERR! gyp verb clean removing "build" directory npm ERR! gyp verb command configure [] npm ERR! gyp verb check python checking for Python executable "/usr/bin/python3" in the PATH npm ERR! gyp verb `which` succeeded /usr/bin/python3 /usr/bin/python3 npm ERR! gyp ERR! configure error npm ERR! gyp ERR! stack Error: Command failed: /usr/bin/python3 -c import sys; print "%s.%s.%s" % sys.version_info[:3]; npm ERR! gyp ERR! stack File "", line 1 npm ERR! gyp ERR! stack import sys; print "%s.%s.%s" % sys.version_info[:3]; npm ERR! gyp ERR! stack ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ npm ERR! gyp ERR! stack SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)? npm ERR! gyp ERR! stack npm ERR! gyp ERR! stack at ChildProcess.exithandler (node:child_process:397:12) npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:390:28) npm ERR! gyp ERR! stack at maybeClose (node:internal/child_process:1064:16) npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5) npm ERR! gyp ERR! System Linux 5.14.16-301.fc35.x86_64 npm ERR! gyp ERR! command "/usr/bin/node" "/home/mehdielghali/Desktop/ganache-ui/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library=" npm ERR! gyp ERR! cwd /home/mehdielghali/Desktop/ganache-ui/node_modules/node-sass npm ERR! gyp ERR! node -v v16.11.1 npm ERR! gyp ERR! node-gyp -v v3.8.0 npm ERR! gyp ERR! not ok npm ERR! Build failed with error code: 1 npm ERR! A complete log of this run can be found in: npm ERR! /home/mehdielghali/.npm/_logs/2021-11-14T02_59_08_900Z-debug.log
  • Dynamic Log Control for Serverless
    5 projects | dev.to | 19 Aug 2021
    To see code samples for Bunyan, Debug, Winston or Python please checkout our Dynamic Logging Samples which has detailed code samples for each library and Python using these techniques.
  • How to install homebridge-config-ui-x on archlinux
    1 project | reddit.com/r/homebridge | 2 Apr 2021
    npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
  • tensorflow install error
    1 project | reddit.com/r/ShinobiCCTV | 30 Mar 2021
    [email protected]:/home/Shinobi/plugins/tensorflow# sh INSTALL.sh Do not attempt to use this Installer on ARM-based CPUs. Removing existing Tensorflow Node.js modules... npm WARN using --force Recommended protections disabled. changed 1 package, and audited 2 packages in 5s found 0 vulnerabilities Shinobi - Do you want to install TensorFlow.js with GPU support? You can run this installer again to change it. (y)es or (N)o n npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future added 235 packages, and audited 236 packages in 1m 5 packages are looking for funding run `npm fund` for details found 0 vulnerabilities npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! Found: @tensorflow/[email protected] npm ERR! node_modules/@tensorflow/tfjs-backend-cpu npm ERR! @tensorflow/[email protected]"2.8.6" from @tensorflow/[email protected] npm ERR! node_modules/@tensorflow/tfjs npm ERR! @tensorflow/[email protected]"2.8.6" from @tensorflow/[email protected] npm ERR! node_modules/@tensorflow/tfjs-node npm ERR! @tensorflow/[email protected]"2.7.0" from the root project npm ERR! @tensorflow/[email protected]"2.8.6" from @tensorflow/[email protected] npm ERR! node_modules/@tensorflow/tfjs-backend-webgl npm ERR! @tensorflow/[email protected]"2.8.6" from @tensorflow/[email protected] npm ERR! node_modules/@tensorflow/tfjs npm ERR! @tensorflow/[email protected]"2.8.6" from @tensorflow/[email protected] npm ERR! node_modules/@tensorflow/tfjs-node npm ERR! @tensorflow/[email protected]"2.7.0" from the root project npm ERR! @tensorflow/[email protected]"2.7.0" from the root project npm ERR! 1 more (the root project) npm ERR! npm ERR! Could not resolve dependency: npm ERR! @tensorflow/[email protected]"2.7.0" from the root project npm ERR! npm ERR! Conflicting peer dependency: @tensorflow/[email protected] npm ERR! node_modules/@tensorflow/tfjs-core npm ERR! peer @tensorflow/[email protected]"2.7.0" from @tensorflow/[email protected] npm ERR! node_modules/@tensorflow/tfjs-backend-cpu npm ERR! @tensorflow/[email protected]"2.7.0" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! See /root/.npm/eresolve-report.txt for a full report. npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2021-03-30T07_13_04_487Z-debug.log added 7 packages, removed 9 packages, changed 2 packages, and audited 234 packages in 36s 5 packages are looking for funding run `npm fund` for details found 0 vulnerabilities npm WARN using --force Recommended protections disabled. up to date, audited 234 packages in 3s 5 packages are looking for funding run `npm fund` for details found 0 vulnerabilities rebuilt dependencies successfully conf.json already exists... Adding Random Plugin Key to Main Configuration key: d7c899d7bec1bd651bfe81ee2948593e29ebec241cdc068e9c0965163223 tfjsBuild: cpu Updating main conf.json with new key. Changes Complete. Here is what it is now. { "plug": "Tensorflow", "host": "localhost", "tfjsBuild": "cpu", "port": 8080, "hostPort": 8082, "key": "d7c899d7bec1bd651bfe81ee2948593e29ebec241cdc068e9c0965163223", "mode": "client", "type": "detector" }

What are some alternatives?

When comparing loggin-js and debug you can also consider the following projects:

node-inspector - Node.js debugger based on Blink Developer Tools

winston - A logger for just about everything.

npm-fast-installer - npm-fast-installer - NPM install configuration in top of YAML for fast NPM install usage.

longjohn - Long stack traces for node.js inspired by https://github.com/tlrobinson/long-stack-traces

dynamodb-onetable - DynamoDB access and management for one table designs with NodeJS

urix - [DEPRECATED] Makes Windows-style paths more unix and URI friendly.

ndb - ndb is an improved debugging experience for Node.js, enabled by Chrome DevTools

swagger-stats - API Observability. Trace API calls and Monitor API performance, health and usage statistics in Node.js Microservices.

bugger - Bugs bugging you? Bug back.

jstrace - Dynamic tracing for javascript, in javascript (similar dtrace, ktap etc)

TraceGL - TraceGL MPL release

ironNode - Debug Node.js code with Chrome Developer Tools.