Loading SES fails if globalThis.process is shimmed

[mhofman]

Describe the bug

Console taming assumes that if globalThis.process exists, then we're in node, and get to use some process APIs like .on() .exit() etc.

endo/packages/ses/src/error/tame-console.js

Lines 97 to 126 in 2179108

	// Node.js
	if (errorTrapping !== 'none' && globalThis.process !== undefined) {
	globalThis.process.on('uncaughtException', error => {
	// causalConsole is born frozen so not vulnerable to method tampering.
	ourConsole.error(error);
	if (errorTrapping === 'platform' || errorTrapping === 'exit') {
	globalThis.process.exit(globalThis.process.exitCode || -1);
	} else if (errorTrapping === 'abort') {
	globalThis.process.abort();
	}
	});
	}
	if (
	unhandledRejectionTrapping !== 'none' &&
	globalThis.process !== undefined
	) {
	const handleRejection = reason => {
	// 'platform' and 'report' just log the reason.
	ourConsole.error('SES_UNHANDLED_REJECTION:', reason);
	};
	// Maybe track unhandled promise rejections.
	const h = makeRejectionHandlers(handleRejection);
	if (h) {
	// Rejection handlers are supported.
	globalThis.process.on('unhandledRejection', h.unhandledRejectionHandler);
	globalThis.process.on('rejectionHandled', h.rejectionHandledHandler);
	globalThis.process.on('exit', h.processTerminationHandler);
	}
	}

If globalThis.process is shimmed with something like {env: {FOO: 'bar'}}, then loading SES fails with globalThis.process.on is not a function.

Expected behavior

Console taming should more fully feature test the Node features it expects

Platform environment

Browser

Screenshots