focomoso Posted February 7, 2017 Share Posted February 7, 2017 Hi, I forked the main repo and was able to build on one machine, but when I cloned to another machine, I'm getting an error with gulp-uglify: events.js:161 throw er; // Unhandled 'error' event ^ Error at new JS_Parse_Error (eval at <anonymous> (/Users/jkelly/dev/Babylon.js/Tools/Gulp/node_modules/gulp-uglify/node_modules/uglify-js/tools/node.js:28:1), <anonymous>:1534:18) at js_error (eval at <anonymous> (/Users/jkelly/dev/Babylon.js/Tools/Gulp/node_modules/gulp-uglify/node_modules/uglify-js/tools/node.js:28:1), <anonymous>:1542:11) at croak (eval at <anonymous> (/Users/jkelly/dev/Babylon.js/Tools/Gulp/node_modules/gulp-uglify/node_modules/uglify-js/tools/node.js:28:1), <anonymous>:2089:9) at eval (eval at <anonymous> (/Users/jkelly/dev/Babylon.js/Tools/Gulp/node_modules/gulp-uglify/node_modules/uglify-js/tools/node.js:28:1), <anonymous>:2239:21) at eval (eval at <anonymous> (/Users/jkelly/dev/Babylon.js/Tools/Gulp/node_modules/gulp-uglify/node_modules/uglify-js/tools/node.js:28:1), <anonymous>:2136:24) at eval (eval at <anonymous> (/Users/jkelly/dev/Babylon.js/Tools/Gulp/node_modules/gulp-uglify/node_modules/uglify-js/tools/node.js:28:1), <anonymous>:2904:23) at Object.parse (eval at <anonymous> (/Users/jkelly/dev/Babylon.js/Tools/Gulp/node_modules/gulp-uglify/node_modules/uglify-js/tools/node.js:28:1), <anonymous>:2915:7) at /Users/jkelly/dev/Babylon.js/Tools/Gulp/node_modules/gulp-uglify/node_modules/uglify-js/tools/node.js:71:33 at Array.forEach (native) at Object.exports.minify (/Users/jkelly/dev/Babylon.js/Tools/Gulp/node_modules/gulp-uglify/node_modules/uglify-js/tools/node.js:66:15) Does anyone have any thoughts on what's going on? Thanks Quote Link to comment Share on other sites More sharing options...
focomoso Posted February 8, 2017 Author Share Posted February 8, 2017 I think this is a versioning error. Is there a specific version of node that the gulp file is expecting? Quote Link to comment Share on other sites More sharing options...
GameMonetize Posted February 8, 2017 Share Posted February 8, 2017 Hello my first try in this kind of cases is to remove the node_modules folder and run a npm install again Quote Link to comment Share on other sites More sharing options...
focomoso Posted February 9, 2017 Author Share Posted February 9, 2017 Thanks, I deleted the entire repo and cloned again and everything's fine. Don't know what the issue was, but it's all good now... GameMonetize 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.