debug
cosmiconfig
Our great sponsors
debug | cosmiconfig | |
---|---|---|
26 | 5 | |
10,994 | 3,828 | |
0.4% | 1.1% | |
3.6 | 8.3 | |
7 months ago | about 2 months ago | |
JavaScript | TypeScript | |
MIT License | MIT License |
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.
cosmiconfig
-
topoconfig: enhancing config declarations with graphs
Meanwhile, formats have been evolving (JSON5, YAML), config entry points are constantly changing. These fluctuations, fortunately, were covered by tools like the cosmiconfig.
-
Moving all config files to a config folder in React?
I've heard of cosmicconfig, which I think allows you to put most of your config files in a single .config folder. I've never used it though.
-
Create a Node.js command-line library with NRWL NX workspace
There is a fantastic library davidtheclark/cosmiconfig: Find and load configuration from a package.json property, rc file, or CommonJS module that does all the tedious work for you.
-
Rob Pike: âDotfilesâ being hidden is a UNIXv2 mistake (2012)
info on XDG: [the XDG spec](https://standards.freedesktop.org/basedir-spec/basedir-spec-...)
tools that respect XDG, for fellow JS CLI developers:
- https://github.com/davidtheclark/cosmiconfig Find and load configuration from a package.json property, rc file, or CommonJS module. [Check `searchPaths` to implement XDG spec compliance.](https://github.com/davidtheclark/cosmiconfig/issues/152)
- Sindre's libraries use [`env-paths`](https://github.com/sindresorhus/env-paths#pathsconfig) to get paths compliant with this.
- https://github.com/sindresorhus/conf simple config storing (maybe try [conf-cli](https://github.com/natzcam/conf-cli) to manipulate if needed) the successor to [configstore](https://github.com/sindresorhus/conf#how-is-this-different-f...)
- https://github.com/jonschlinkert/data-store conf like datastore but in the shclinkerverse
-
A Node.js configuration provider reading files, environment and arguments
cosmiconfig - Reads configuration from a file. It searches for many file types and file names, and even supports defining config in the package.json file. Very customizable, it's an awesome library very flexible both for the app developer and for the app user.
What are some alternatives?
node-inspector - Node.js debugger based on Blink Developer Tools
main - Node.js mock server running live, interactive mocks in place of real APIs
npm-fast-installer - npm-fast-installer - NPM install configuration in top of YAML for fast NPM install usage.
Commander.js - node.js command-line interfaces made easy
bugger - Bugs bugging you? Bug back.
data-store - Easily get, set and persist config data. Fast. Supports dot-notation in keys. No dependencies.
ndb - ndb is an improved debugging experience for Node.js, enabled by Chrome DevTools
conf-cli - simple cli for configuration and key/value's + oclif plugin for configuration
longjohn - Long stack traces for node.js inspired by https://github.com/tlrobinson/long-stack-traces
config - Helps you find, load, combine, autofill and validate configuration values of any kind
swagger-stats - API Observability. Trace API calls and Monitor API performance, health and usage statistics in Node.js Microservices.
misc - Experiment on maintaining a multi-project monorepository