9.18.0 introduces a dependency on a public repository which fails on machines without Git installed

[raglan-road]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/nextjs

SDK Version

9.18.0

Framework Version

No response

Link to Sentry event

No response

Reproduction Example/SDK Setup

No response

Steps to Reproduce

• Install or update Sentry to 9.18.0 on a VM without Git installed. For example, the nodejs Alpine linux distro.
• Run an npm install or a build.
• When the Sentry package attempts to install the @fastify/otel dependency, it does so using Git, which isn't there, so the install fails.

Expected Result

Sentry is able to load its dependencies and the build succeeds or the requirement for Git to be installed on the target machine is documented as a potentially breaking change.

Actual Result

The build fails when the Sentry package attempts to install its dependency on the forked version of @fastify/otel as it installs via Git, which does not necessarily exist on the target machine.

Rolling back to 9.16.1 fixes the issue as the new dependency isn't there.

[andreiborza]

Hi @raglan-road, thanks for filing this.

Can confirm, it indeed fails to install because of our @fastify/otel fork. Will look into it.

[jpmcb]

+1 - I would consider this a major regression - this breaks packages that depend on @sentry/node and don't pin to an older version which, before 9.18, worked with no dependency on git (like Windows machines, Macs that don't have Xcode dev tools setup, VSCode dev containers, etc. etc.):

Replication steps:

1. Start fedora 43 container

docker run -it --rm fedora:43 /bin/bash

2. Install node

dnf install nodejs22

3. Attempt to install sentry node package:

bash-5.2# npm i -g @sentry/node
npm error code ENOENT
npm error syscall spawn git
npm error path git
npm error errno -2
npm error enoent An unknown git error occurred
npm error enoent This is related to npm not being able to find a file.
npm error enoent
npm error A complete log of this run can be found in: /root/.npm/_logs/2025-05-13T22_14_22_036Z-debug-0.log

[andreiborza]

Thanks, we'll release a fix soon.