fix: handle sev logger esm callsites#131
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.
Why
A clean install of
@transloadit/sev-logger@1.0.0could import the package, but actually logging with the default callsite formatter threwCould not get dirnamewhen Node emittedfile://ESM stack frames. This patch fixes the runtime path detection and releases1.0.1.What changed
import.meta.filenameas the logger's own file path instead of parsing it from a stack trace.file://callsite paths before formatting them.notice()with callsite detection enabled.@transloadit/sev-loggerto1.0.1with a changelog entry.Verification
corepack yarn install --immutablecorepack yarn dedupe --checkcorepack yarn checkcorepack yarn npm audit --recursive --allgit diff --checkdistsmoke test that imports@transloadit/sev-loggerand callsnotice()