Skip to content

@sentry/node should not have a direct dependency on @sentry/tracing #4642

Closed
@timfish

Description

@timfish

Problem Statement

It seems like @sentry/tracing is a direct dependency of @sentry/node due to only this single line:

import { extractTraceparentData, Span } from '@sentry/tracing';

This has a number of downsides:

  • There are side effects that users will be unaware of
  • The Node performance docs are outdated saying you need to import @sentry/tracing
  • @sentry/tracing now accounts for nearly 50% of the Node SDK init time
    • Run this to get cpu profile: node --cpu-prof -e "require('@sentry/node').init({dsn:'http://some@real.dsn/123'})"

Solution Brainstorm

Inline that code?

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions