DK uses deprecated url.parse() API which triggers Node.js DEP0169 warnings on every cold start. Functional impact: none. Log noise impact: medium.

[mromeruyar]

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/node

SDK Version

10.52.0

Framework Version

Custom/Vanilla Node Node.js version 22.x Vercel Serverless Func. Vercel Runtime 20.x

Link to Sentry event

No response

Reproduction Example/SDK Setup

// api/_sentry.js (bizim kurulum)
import * as Sentry from "@sentry/node";

Sentry.init({
dsn: process.env.SENTRY_DSN_SERVER,
environment: process.env.VERCEL_ENV ?? "development",
tracesSampleRate: 0.1,
});

// Used to wrap Vercel serverless handlers:
export function wrapHandler(handler) {
return async (req, res) => {
try {
return await handler(req, res);
} catch (err) {
Sentry.captureException(err);
await Sentry.flush(2000);
}
};
}

Steps to Reproduce

npm install @sentry/node@10.52.0

// api/test.js
import * as Sentry from "@sentry/node";
Sentry.init({ dsn: process.env.SENTRY_DSN, tracesSampleRate: 0.1 });
export default async function handler(req, res) {
await fetch("https://api.example.com/data"); // Triggers HTTP instrumentation
res.json({ ok: true });
}

Deploy to Vercel, hit the endpoint

Expected Result

(node:4) [DEP0169] DeprecationWarning: url.parse() behavior is not standardized
and prone to errors that have security implications. Use the WHATWG URL API instead.
CVEs are not issued for url.parse() vulnerabilities.
(Use node --trace-deprecation ... to show where the warning was created)

Actual Result

2026-05-08 16:32:09.990 [error] (node:4) [DEP0169] DeprecationWarning: url.parse() behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for url.parse() vulnerabilities.

Additional Context

No response

Priority

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

[linear-code]

JS-2422