Closed vizv closed 6 years ago
babel-node spawn its own sub-process which generates a isolate log that 0x is not able to locate.
To resolve such a issue, timestamp might be used as a clue for locating those isolate logs generated with non-standard 0x.
Tested with 0x -o -- babel-node --prof foo.js.
0x -o -- babel-node --prof foo.js
Not working when presets was added, close for now
please ignore this PR, babel works with 0x -- node --require babel-register --require babel-polyfill index.js
0x -- node --require babel-register --require babel-polyfill index.js
babel-node spawn its own sub-process which generates a isolate log that 0x is not able to locate.
To resolve such a issue, timestamp might be used as a clue for locating those isolate logs generated with non-standard 0x.
Tested with
0x -o -- babel-node --prof foo.js
.