René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"What will Domain be replaced with?","articleBody":"I'm adding support for parallel tests to node-tap.  https://github.com/tapjs/node-tap/issues/306\r\n\r\nOne sticky point is that, like most test frameworks, node-tap needs to be able to cleverly handle thrown errors and tie them to the test environment where the error was thrown from (especially since many existing assertion libs turn things like `expect(foo).to.match(/regexp/)` into a thrown error).\r\n\r\nWhen tests were _not_ run in parallel, there was no problem.  Just walk down the tree of `test.currentChild` or whatever, and a single `process.on('uncaughtException')` is sufficient.\r\n\r\nI'm using Domains to manage thrown errors in child tests, and it works great, but the bright red deprecation notice in [the docs](https://nodejs.org/api/domain.html#domain_domain) is scary.\r\n\r\nWhat will it be replaced with?  Will it be feature-equivalent?  If so, is there any reason why the existing API has to be broken, and not re-implemented in terms of the new thing?  Is there an expected time frame for the Domain api to be broken?\r\n\r\nThanks.","author":{"url":"https://github.com/isaacs","@type":"Person","name":"isaacs"},"datePublished":"2017-01-17T00:22:15Z","url":"https://github.com/nodejs/node/issues/10843"}