GeezerVison

On Node < 24.13, the CJS build of register.ts passed build/esm/hook.js to Module.register(). Turbopack ships that file in the Next.js server trace but does not follow its imports, so the loader thread could not find build/esm/vendored/** or the ESM build of @sentry/core. Registration then warned on every cold start.

The CJS build now registers build/cjs/hook.js, which the package already built but did not use. That file only requires chunks that register.js requires too, so a tracer that ships a working register.js always ships them. Node accepts a CJS module as a Module.register() target. This is an alternative to #26271: the package does not grow and no Next.js config is needed.

The data: URL loader that forced the ESM format for build/esm is removed. It only helped the CJS build load the ESM hook when a deployment dropped build/esm/package.json, and the CJS build no longer loads anything from build/esm. The ESM build still registers the ESM hook.

The new test/hook.test.ts registers the hook from a copy that ships only build/cjs. The nextjs-16-standalone build-output test (taken from #26271) forces the Module.register() path against the real Turbopack standalone output. Both fail on develop with the error from the issue.

Closes #26121