-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError: eval is not a function #30
Comments
The |
Then why am I getting this error on app start on 2 different computers, with 2 different Node.js versions? In the current case I'm using: Node.js v8.11.4 (latest LTS on their site is v8.12.0) I'm not using Electron, NW.js or anything else, just Node.js |
Also, I had no problems in the past, this started happening recently. |
I'm not sure. I just tried it out and the function is there still for me:
and
Perhaps if you can provide the full steps to reproduce on my end I can help determine why you're having the issue, but without any steps to reproduce, you'll likely need to debug through it or open an issue on the Node.js repo if your binaries are missing a core function. |
One would also think that your report wouldn't be the first and only one (https://github.com/dougwilson/nodejs-depd/issues?utf8=%E2%9C%93&q=is:issue+%22eval+is+not+a+function%22) if |
This is indeed very strange, your terminal command works for me too:
But I can't imagine how that error could mean anything else, or be caused by anything else. I'll try to make a simplistic test case to see if it's reproducible on a small scale, otherwise it may be that my app is somehow breaking it, although i can't currently comprehend how it could break |
holy mother of god, i debugged it and found the issue, thanks for taking the time to put me straight for your enjoyment, i was using a deobfuscation script found online, which after reading it thoroughly, it does, and I quote:
jesus christ.. it's annoying that it proved itself to be the best deobfuscation script out there |
What the what? That is pretty mind blowing. I'm glad you found the issue. I would have been happy to re-open if there was something we had to change to fix something, of course 👍 |
Recently my app keeps exploding because of this error from
depd
:I think
node.js
removedeval()
completely in favor ofVM
: https://nodejs.org/api/vm.htmldepd
is a dep of a lot of modules in my case:express
,http-errors
,send
andbody-parser
So, my question is why is depd v2.x not being released already to solve this mayhem properly?
The text was updated successfully, but these errors were encountered: