Skip to content

Conversation

@AbhiPrasad
Copy link
Member

ref #15952

resolves #16621

We've gotten a lot of feedback about supporting pino. This PR kicks that off by creating a new pino package, specifically for the pino transport.

All pino transports need to use https://github.com/pinojs/pino-abstract-transport, which we don't want to add as a dep to @sentry/node. Hopefully keeping the versions in sync shouldn't be too bad, although I'll force a peer dep range.

@AbhiPrasad AbhiPrasad requested a review from a team June 18, 2025 23:59
@AbhiPrasad AbhiPrasad self-assigned this Jun 18, 2025
@AbhiPrasad AbhiPrasad requested review from andreiborza and mydea and removed request for a team June 18, 2025 23:59
},
"dependencies": {
"@sentry/core": "9.30.0",
"@sentry/node": "9.30.0"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

q: Should the node sdk be a dependency?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it shouldn't - we can remove!

@AbhiPrasad AbhiPrasad enabled auto-merge (squash) June 20, 2025 12:34
@AbhiPrasad AbhiPrasad merged commit 4bbe610 into develop Jun 20, 2025
163 checks passed
@AbhiPrasad AbhiPrasad deleted the abhi-pino-package branch June 20, 2025 12:51
AbhiPrasad added a commit that referenced this pull request Oct 2, 2025
This package was added in
#16652, but with the
merge of #17584 we
can remove it. We will recommend users use the `pinoIntegration` because
it's way easier to set up and tracing works ootb.

This package was never published (no craft config) so it's safe to
remove.
andreiborza pushed a commit to thedanchez/sentry-javascript that referenced this pull request Oct 15, 2025
This package was added in
getsentry#16652, but with the
merge of getsentry#17584 we
can remove it. We will recommend users use the `pinoIntegration` because
it's way easier to set up and tracing works ootb.

This package was never published (no craft config) so it's safe to
remove.
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.

Create pino transport package

2 participants