Skip to content

fix: avoid nodejs stream namespace leak#132

Merged
kvz merged 1 commit into
mainfrom
sev-stream-types
May 28, 2026
Merged

fix: avoid nodejs stream namespace leak#132
kvz merged 1 commit into
mainfrom
sev-stream-types

Conversation

@kvz
Copy link
Copy Markdown
Member

@kvz kvz commented May 28, 2026

Why

The all-packages consumer smoke showed that runtime installs work, but @transloadit/sev-logger still leaked NodeJS.WriteStream through its public declarations. That makes TypeScript consumers depend on a global NodeJS namespace even when they only need the logger's stream contract.

What changed

  • Added a structural SevLoggerStream interface for the logger's stdout/stderr options and properties.
  • Exported SevLoggerStream from the package root.
  • Versioned @transloadit/sev-logger to 1.0.2 with a changelog entry.

Verification

  • corepack yarn install --immutable
  • corepack yarn dedupe --check
  • corepack yarn check
  • corepack yarn npm audit --recursive --all
  • git diff --check
  • Local tarball TypeScript consumer smoke without @types/node

@kvz kvz merged commit 3ced69f into main May 28, 2026
2 checks passed
@kvz kvz deleted the sev-stream-types branch May 28, 2026 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant