Open legendecas opened 1 year ago
Thanks for opening this @legendecas. Do you have any plan or idea for next steps towards a NodeRealm
?
I'm experimenting with a local setup to expose Web globals like URL
in ShadowRealm (based on https://github.com/nodejs/node/pull/46556). I believe many infrastructures can be shared between ShadowRealm and the NodeRealm
. The following steps for NodeRealm
can be:
createRequire
from the outer realm).import
from the outer realm).vm.Script
and vm.Module
)NodeRealm
(Similar to https://docs.google.com/document/d/12_CkX6KbM9kt_lj1pdEgLB8-HQaozkJb7_nwQnHfTTg/edit#heading=h.drlp0amd3twr):
globalThis.process
events like uncaughtException
and unhandledRejection
.node:v8
and process.exit
.NodeRealm
:
NodeRealm
.Regarding process.exit()
: it should "close" the Realm, similarly to how it works in worker_threads
This is sorta #28823 and #31852, right?
@SimenB This is sorta https://github.com/nodejs/node/issues/28823 and https://github.com/nodejs/node/issues/31852, right?
Effectively, yes.
There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment.
For more information on how the project manages feature requests, please consult the feature request management document.
There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment.
For more information on how the project manages feature requests, please consult the feature request management document.
There has been no activity on this feature request for 5 months. To help maintain relevant open issues, please add the https://github.com/nodejs/node/labels/never-stale label or close this issue if it should be closed. If not, the issue will be automatically closed 6 months after the last non-automated comment. For more information on how the project manages feature requests, please consult the feature request management document.
Scripts/Modules running in the context created with
vm.createContext
can not access various Node.js built-in apis/modules likeURL
,node:assert
,node:http
, etc. This makes it cumbersome to create a disposable context for use cases like hot-module-reload to run existing node.js apps.We can provide a built-in API to create a
context
(or a newNodeRealm
for compatibility) with full-fledged Node.js built-in modules support. It allows object exchanges between realms and shares the same loop with the main context. , similar to the existingvm.context
./cc @mcollina @nodejs/realm @nodejs/vm