async-object-stack
Advanced tools
Comparing version 1.0.0-beta.1 to 1.0.0
@@ -1,6 +0,6 @@ | ||
## Structural Logging Example | ||
# Structural Logging Example | ||
This example shows how to use `async-object-stack` to implement an easy to use structural logging system. | ||
### How to run | ||
## How to run | ||
@@ -19,3 +19,3 @@ Build TypeScript by `npx tsc` and run `node dist/examples/logger/index.js` to invoke an HTTP server on port 8080. | ||
### What is structural logging? | ||
## What is structural logging? | ||
@@ -28,3 +28,3 @@ **Structural logging** is a logging system where each log entry can contain arbitrary metadata in addition to log message. The benefit of structural logging is that you can easily filter and aggregate logs by metadata. | ||
### Using `async-object-stack` | ||
## Using `async-object-stack` | ||
@@ -52,3 +52,3 @@ `async-object-stack` utilizes `AsyncLocalStorage` to provide a simple interface to manage the context. Its API is specialized for managing the context as a stack of objects which can be rendered into one object at any time. Since log metadata is usually represented as an object, this API is a good fit for structural logging. | ||
### Using `region` | ||
## Using `region` | ||
@@ -55,0 +55,0 @@ When you use `async-object-stack`, it is important to understand the concept of `region`. Failing to use `region` correctly can lead to unwanted and weird behavior where the context is shared across unrelated tasks. |
{ | ||
"name": "async-object-stack", | ||
"version": "1.0.0-beta.1", | ||
"version": "1.0.0", | ||
"description": "Stacked objects in async call stack", | ||
@@ -36,2 +36,2 @@ "author": "uhyo <uhyo@uhy.ooo>", | ||
} | ||
} | ||
} |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
No v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
77338
54
1363
1