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
the eval at the heart of the test routine is relative to the CLI script. I think there's a similar issue when we have {output: "parser"} in the API.
Some combination of vm and require("module").createRequire (when it's available) might be needed. Probably also making __dirname and __filename match the outputFile if it's not "-", and using cwd and a synthetic name when it is "-".
In node 10, createRequire doesn't exist, but the undocumented createRequireFromPath does, as well as new Module(path).require.
I don't know how to fix this for import, but we can probably at least hack in import.meta.url same as __filename.
The text was updated successfully, but these errors were encountered:
In a directory other than
<PEGGY_ROOT>/bin
, this fails:the
eval
at the heart of the test routine is relative to the CLI script. I think there's a similar issue when we have{output: "parser"}
in the API.Some combination of
vm
andrequire("module").createRequire
(when it's available) might be needed. Probably also making__dirname
and__filename
match the outputFile if it's not "-", and using cwd and a synthetic name when it is "-".In node 10,
createRequire
doesn't exist, but the undocumentedcreateRequireFromPath
does, as well asnew Module(path).require
.I don't know how to fix this for
import
, but we can probably at least hack inimport.meta.url
same as__filename
.The text was updated successfully, but these errors were encountered: