Marcel Beerta

unfortunately not, but i had the same thoughts of making this switchable. Might be reusing the --preserve-symlinks option a viable approach (although it is also passed to the node runtime)?

We are running into a similar issue here, using url or discrete options causes this to appear just after `connect()` is called. ``` node:internal/process/promises:288 triggerUncaughtException(err, true /* fromPromise */); ^...