Roadmap for stabilization of vm modules
Open
Nobody has claimed this yet.
esm
experimental
help wanted
loaders
never-stale
vm
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the unchecked linked issues, especially #35714, #43899, #31234, #33216, #60242, and source phase import support. The Jest tracking issue at https://github.com/jestjs/jest/issues/9430 provides additional context. Done means the remaining stabilization blockers are resolved and the vm modules can be unflagged as stable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100