According to @SimenB, here are the issues that should probably be taken care of before we unflag and mark vm modules as stable:

• vm.Script's importModuleDynamically should get a reference to the context used to run it (#35714)
• Simplify vm.Module #43899
• Provide built-in implementations of module linker, initializeImportMeta, importModuleDynamically #31234
• VM ESM with dynamic imports resolves promises before linking is complete (#33216)
• vm.Module.evaluate() morphs loader errors into module evaluation rejections #60242
• Link modules with paths in module.link(linker) #35848
• Provide built-in implementations of module linker, initializeImportMeta, importModuleDynamically #31234
• Improve performance of accessing globals in scripts running in vm modules #31658
• SourceTextModule memory leak (#33439)
• Segmentation fault with import() instead of calling importModuleDynamically (#35889)
• importModuleDynamically for vm module is cached (#36351)
• SourceTextModule leaks memory when context is used #50113
• vm.SourceTextModule memory leak #59118
• Provide SourceTextModule sync versions of link and evaluate methods #59656
• SourceTextModule: Using dynamic imports while passing cachedData throws TypeError: Invalid host defined options #43663
• Change API of module.lnk((specifier) => module) to module.link(specifiers, modules) so that it has fewer C++ -> JS calls and can be reused to implement require(esm).
• Source phase import support.

Tracking issue in Jest: jestjs/jest#9430
/cc @devsnek