-
Notifications
You must be signed in to change notification settings - Fork 38
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
Throws error with Node.js 13.6 #28
Comments
I've also run into this one when updating from Node 12.7 to 13.9, but I found that going back as far as 12.16 didn't help - I had to go back to 12.7 before the problem went away for me. |
Having the same issue while running a gulp task over a Azure Devops pipeline, any fix apart from downgrading node? |
Hi, after checking out the javascript-obfuscator repo, I found out this bug was patched out on version v0.18.8 and is caused by the "events" module (check out javascript-obfuscator/javascript-obfuscator#452) In my case, I just made a reference to the newest version of javascript-obfuscator (0.25.2) on my npm file and the error disappeared. |
I can confirm that I got the same issue and was able to resolve it until using NVM to fallback to an older version of Node after a fresh install of one of my projects on my resetted laptop. |
The fix is to use the command 'npm remove' for gulp-javascript-obfuscator and then do 'npm install --save gulp-javascript-obfuscator'. This forces a refresh of the libraries it is dependent on. Adding javascript-obfuscator to your package.json might not resolve this issue. |
After upgrading to Node.js version 13.6 running our Gulp task with gulp-javascript-obfuscator in it throws the following error:
Running npm install from scratch doesn't resolve this error. Works fine as soon as you switch back to Node.js 13.3.
The text was updated successfully, but these errors were encountered: