Daeyeon Jeong

On second thought, validating the `process.exitCode` seems to be a better approach for `process.exit([code])`. 1. The following case is still possible since there is no validation on `process.exitCode`. ```js process.exitCode...

I left the conflicts on purpose for easy review.

Thanks for reminding our deprecation process. :-) I'll do the follow-up after the next major release.

Oh now I got it. I'll prepare a PR for a runtime deprecation so that it can be landed before the cutoff.

While rebasing the code I've squashed the previous commits because of many conflicts in several fixup commits. I will rebase this PR again once the release version for runtime deprecation...

The runtime deprecation has been versioned as v19.0.0. Rebased to resolve a conflict from the change.

/cc @nodejs/whatwg-stream

Sure. I plan to open a PR that contains all commits related to `test/wpt/status/streams.json`.

Please update https://github.com/nodejs/node/blob/main/doc/node.1 also.

https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=benchmark-ubuntu2204-intel-64,v8test=v8test/5945/ The CI test error seems to require a fix for #51308. ``` 12:20:46 1480c755c560 8 JS:~functionTwo /home/iojs/build/workspace/node-test-commit-v8-linux/test/fixtures/linux-perf-logger.js:13:21 12:20:46 1480c755c600 3c JS:~functionOne /home/iojs/build/workspace/node-test-commit-v8-linux/test/fixtures/linux-perf-logger.js:7:21 12:20:46 12:20:46 12:20:46 12:20:46 at runSuite (/home/iojs/build/workspace/node-test-commit-v8-linux/test/v8-updates/test-linux-perf-logger.js:145:10)...