Sentry upgrades break working setups

2 posts from 2 people2d activeFading, +0 this weekunverified

Posts per day2 posts, Sep 16 to Nov 9

The posts behind it

GitHub issuesvercel/next.js · miedzikdNov 2

Turbopack production build: "Compiled successfully" takes 6–8 min on 16.4.x vs 15 s on 16.3.8 and 12 s on 16.5.0-canary.36 (same app, 3k modules)

### Summary On a mid-sized app, `next build` (Turbopack) is about 30× slower on 16.4.x than on 16.3.8, and the problem is already fixed on the 16.5 canary line. 16.3.8 is not an option for us (it has open advisories), and 16.4.3 / 16.4.4 do not help, so we would like to ask...

1 replies

GitHub issuesvercel/next.js · ChrisCampbellCodesSep 16

experimental.testProxy: passthrough fetch to an HTTPS origin with a streaming body aborts the Node process (regression in 16.3)

...the same function `next start` calls when `experimental.testProxy` is enabled, and the failing branch is the passthrough branch of `handleFetch`, which is what an MSW `passthrough()` handler resolves to.

1 replies

Companies and products named

Sentry

2 posts

Vercel

2 posts

npm

1 post

About this problem

Evidence

2 posts from 2 people in 1 place, about 1 a week over 48 days. Mostly on vercel/next.js. Tools named alongside: Vercel, npm.

Frustration Frustration 0 of 3· Seen on GitHub issues

How it was grouped

Posts that state a pain and match the "breaking-changes" rule about Sentry. First post Sep 16, 2026, latest Nov 2, 2026. Unverified: fewer than 3 posts, or one person or place only. Method

The same problem elsewhere