Bristol
Bristol copied to clipboard
TomFrost
Insanely configurable logging for Node.js
For certain messages, it's not interesting where they originate from (file:line). One example would be startup messages: logger.info("We're up and running"); // the filepath:line is not interesting Fortunately, though this...
When logging an object with the human formatter, I see that the output is different in nested object keys and values, vs. root ones: * keys are quoted in nested...
Hi @TomFrost, Just wanted to check if you still have plans to maintain this package. I'm an OSS developer myself and have my fair share of packages I had to...
Can you make a `types/@bristol` pull request or add a `index.d.ts` file to the repo and do an npm release please? I have this I believe: ``` interface LogError {...
Bristol 1.0
# Bristol 1.0 The 1.0 release of Bristol is in the works, and will be a major breaking release with a focus on performance, flexibility, and configurability. ## Shortcomings of...
Is it possible to add/support the use of colors with a human readable console target, similar to how npm logs colors? I find it significantly helps with ease of quickly...
I'm trying to build a target for a cloud logging system (Rollbar) that accepts object parameters in its log calls, and parses that object and displays individual keys in the...
@TomFrost Love Bristol, been using it for a long time. I recently came across a need to obfuscate my file paths. I found that this was relevant for live demos...
``` import logger from 'bristol'; logger.addTarget('console'); logger.addTarget('file', { file: 'bristol.log', }); logger.info('Not logged to the file'); process.exit(1); ``` Winston has [the same issue](https://github.com/winstonjs/winston/issues/228).