esmexperimentalhelp wantedloadersnever-stalevm
Repository-Metriken
- Stars
- (117.218 Stars)
- PR-Merge-Metriken
- (Durchschn. Merge 18T 17h) (219 gemergte PRs in 30 T)
Beschreibung
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'simportModuleDynamicallyshould get a reference to thecontextused to run it (#35714) - https://github.com/nodejs/node/issues/43899
- https://github.com/nodejs/node/issues/31234
- VM ESM with dynamic imports resolves promises before linking is complete (#33216)
- https://github.com/nodejs/node/issues/60242
- https://github.com/nodejs/node/issues/35848
- https://github.com/nodejs/node/issues/31234
- https://github.com/nodejs/node/issues/31658
- SourceTextModule memory leak (#33439)
- Segmentation fault with
import()instead of callingimportModuleDynamically(#35889) - importModuleDynamically for vm module is cached (#36351)
- https://github.com/nodejs/node/issues/50113
- https://github.com/nodejs/node/issues/59118
- https://github.com/nodejs/node/issues/59656
- https://github.com/nodejs/node/issues/43663
- Change API of
module.lnk((specifier) => module)tomodule.link(specifiers, modules)so that it has fewer C++ -> JS calls and can be reused to implementrequire(esm). - Source phase import support.
Tracking issue in Jest: https://github.com/jestjs/jest/issues/9430 /cc @devsnek