You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #17560, we added the ability for users to created their own ECMAScript Modules with the vm.Module class (more information can be found in the documentation). However, as of right now the import.meta exposed in vm.Modules is always an empty object:
>module=newvm.Module('import.meta')Module{status: 'uninstantiated',linkingStatus: 'unlinked',url: 'vm:module(0)',context: undefined}>(node:22093) ExperimentalWarning: vm.Moduleisanexperimentalfeature.Thisfeaturecouldchangeatanytime>awaitmodule.link(()=>{})undefined>module.instantiate()undefined>var{ result }=awaitmodule.evaluate()undefined>result{}
Ideally, we would like the callers of vm.Module to be able to customize what import.meta contains in the created module.
The text was updated successfully, but these errors were encountered:
TimothyGu
added
vm
Issues and PRs related to the vm subsystem.
esm
Issues and PRs related to the ECMAScript Modules implementation.
labels
Feb 4, 2018
In #17560, we added the ability for users to created their own ECMAScript Modules with the
vm.Module
class (more information can be found in the documentation). However, as of right now theimport.meta
exposed invm.Module
s is always an empty object:Ideally, we would like the callers of
vm.Module
to be able to customize whatimport.meta
contains in the created module.The text was updated successfully, but these errors were encountered: