Open nippur72 opened 8 years ago
I encountered the same problem when I trying to evaluate a piece of string which contains calls to React.createElement
. And I found the reason is that node-eval
used vm which created an entirely new context:
const evaluate = require('eval');
const O2 = evaluate("module.exports = Object;");
console.log(O2 === Object); // output false
The solution is to prevent usage of vm
or just use vm.runInThisContext
. Additionally, I found another package named require-from-string
doesn't have the problem since it used a different approach to load values from strings.
I have the following
react
code running in node.js:but react complains that
Does anybody knows why this is happening and is there something I can do?
Of course there is no warning if I execute outside of
_eval
. I should mention also that the above warning was introduced with https://github.com/facebook/react/pull/6134