lib vm: testcase demonstrating issue 59541

Check that we lose the execution flow in the outer context, upon
resolving a promise created in in the inner context.

Author: ericrannaud

test/parallel/test-vm-module-after-evaluate.js

@@ -0,0 +1,29 @@
+// Flags: --experimental-vm-modules
+'use strict';
+
+// https://github.com/nodejs/node/issues/59541
+//
+// Promises created in a context using microtaskMode: "aferEvaluate" (meaning
+// it has its own microtask queue), when resolved in the surrounding context,
+// will schedule a task back onto the inner context queue. This test checks that
+// the async execution progresses normally.
+
+const common = require('../common');
+const assert = require('assert');
+const vm = require('vm');
+
+const context = vm.createContext({}, {
+  microtaskMode: "afterEvaluate",
+});
+
+(async () => {
+  const module = new vm.SourceTextModule(
+    '',
+    {context},
+  );
+
+  await module.link(common.mustNotCall());
+  await module.evaluate();
+})().then(
+    // mustNotCall to illustrate the issue, it should of course be called.
+    common.mustNotCall());

test/parallel/test-vm-script-after-evaluate.js

@@ -0,0 +1,23 @@
+'use strict';
+
+// https://github.com/nodejs/node/issues/59541
+//
+// Promises created in a context using microtaskMode: "aferEvaluate" (meaning
+// it has its own microtask queue), when resolved in the surrounding context,
+// will schedule a task back onto the inner context queue. This test checks that
+// the async execution progresses normally.
+
+const common = require('../common');
+const assert = require('assert');
+const vm = require('vm');
+
+vm.runInNewContext(
+      `Promise.resolve()`,
+      {}, { microtaskMode: 'afterEvaluate' })
+  // We need to first resolve to a native promise object, to hit
+  // the behavior described at
+  // https://issues.chromium.org/issues/441679231
+  .then(Promise.resolve())
+  .then(
+      // mustNotCall to illustrate the issue, it should of course be called.
+      common.mustNotCall());