ref(node): Don't return after process.exit

[AbhiPrasad]

Any code after process.exit(1) is unreachable, so this return statement does nothing. We can remove it safely.

[github-actions]

size-limit report

Path	Base Size (193b2ec)	Current Size	Change
@sentry/browser - CDN Bundle (gzipped)	19.69 KB	19.69 KB	+0.01% 🔺
@sentry/browser - CDN Bundle (minified)	62.91 KB	62.91 KB	+0.01% 🔺
@sentry/browser - Webpack	22.21 KB	22.21 KB	0%
@sentry/browser - Webpack - gzip = false	76.02 KB	76.02 KB	0%
@sentry/react - Webpack	22.24 KB	22.24 KB	0%
@sentry/nextjs Client - Webpack	46.31 KB	46.31 KB	0%
@sentry/browser + @sentry/tracing - CDN Bundle (gzipped)	28.22 KB	28.23 KB	+0.02% 🔺

[lobsterkatie]

TS is happy with this? Once or twice I've come across a stray useless return statement and it's gotten mad when I've pulled it out - "not all code paths return a value," etc, etc. Here I'd hope it'd be smart enough to recognize that exit ends things, but you never know...

UPDATE: I guess if all the checks are passing, it's fine with it. Will mash approve.

[AbhiPrasad]

Yeah it was actually my vscode's TS that complained.

If we look at the node types, we can see that process.exit() returns a never: https://github.com/DefinitelyTyped/DefinitelyTyped/blob/8a401fa673d1593f39151a16c1ca8e60bdee1e94/types/node/process.d.ts#L617, which should instruct the TS compiler that anything below that function call is unreachable code. This functionality was added in 3.7 microsoft/TypeScript#28859 (comment), so idk why it doesn't error. Also we didn't specify a value for allowUnreachableCode.

Might be missing something simple 🤷