Repository navigation
Add isolated async request scopes and redaction for stable v1 - #10
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Node-only /context subpath now provides isolated AsyncLocalStorage request scopes through awaited work and child loggers, with nested restoration and explicit disposal. Redact credential context keys and configured literal values before writer/returned output. Text logs now include context; default key redaction is an intentional documented v1 behavior change.
Validations: lint/format/types, 22 tests and coverage gates,16 concurrent scopes plus nested/error/disposal cases, installed ESM/CommonJS /context runtime and declarations, loopback HTTP example, and five-tool measured workflow. Browser-safe main API stays separate from Node scopes. Final-head Linux22/24, Windows24 and macOS24 CI required.