Issues
- 6
- 2
Can't omit the file path altogether
#53 opened by dandv - 1
- 0
Is this package still maintained?
#61 opened by dandv - 3
Consider using a lighter alternative to Moment
#58 opened by dandv - 0
TypeScript
#59 opened by brandonros - 10
Bristol 1.0
#57 opened by TomFrost - 1
Moment.js vulnerability
#50 opened by marcelcremer - 3
Colorized console output
#14 opened by mfine15 - 0
Pass the unformatted message(s) to the target
#56 opened by dandv - 4
Optionally obfuscate file paths
#28 opened by sjberry - 0
Logs to file not flushed on exit
#55 opened by dandv - 0
- 4
Use json-stringify-safe for json formatter
#35 opened by rooftopsparrow - 0
Dates do not get passed to formatter
#47 opened by jeffijoe - 3
- 1
Child logger support
#46 opened by jeffijoe - 2
A question about Bristol and cluster
#45 opened by jnmichaud - 1
Use splunk
#42 opened by litti - 3
v0.3.3 not at latest on npm
#39 opened by dogfoodsilo4 - 1
Wrong origin when wrapping Bristol
#29 opened by MarkHerhold - 2
Change log level in runtime
#37 opened by mostr - 3
Move standard formatters to public export
#34 opened by rooftopsparrow - 3
Allow targets to be automatically added to default Bristol instance, configured by env vars
#31 opened by TomFrost - 0
Allows targets to be configured by passing an options object, rather than using chained methods
#33 opened by TomFrost - 0
Allow Bristol to be configured entirely through an options object passed to the constructor
#32 opened by TomFrost - 4
Origin logging not correct
#21 opened - 2
Cluster Awareness
#3 opened by dmuth - 0
Logging array values
#10 opened by endorama - 0
- 3
Using bristol with console target in prod
#20 opened by mostr - 2
"TypeError: path must be a string"
#16 opened by Hannessa - 2
limit log file
#8 opened by jimmywarting - 4
Use with Express
#9 opened by unphased - 1
Unable to use addGlobal
#6 opened by augustknight