@Dan-Reyes I am not expert in Nodebb but getting stuck means number of things to me. I usually take some basic steps to get passed build/upgrade issues. You said you reset the plugin already. I would also clean the existing assets in \build\public and rebuild again. (Make sure back up your existing folder before experimenting)
Do you have any custom plugins? If you do, you may have an error that cases uglifier to silently crash. Temporarily modify uglify-es in node-module and change the following in parse.js and run to see if you get any parsing error:
function JS_Parse_Error(message, filename, line, col, pos) {
this.message = message;
this.filename = filename;
this.line = line;
this.col = col;
this.pos = pos;
// add following if not there
console.log('*** Error: File:%s, Line:%d, Col:%d, Pos:%d, message:%s', filename, line, col, pos, message)
};
If you do have error clear it up and try again. Next, you may want to try the upgrade with different options to get to the bottom of this:
nodebb upgrade --help
Some tools like Atom have odd behavior and I recommend to quit them when upgrading.
If nothing works, then you may want to install a fresh copy somewhere else and copy the content and overwrite your working instance. Again make sure to backup your data and custom work whatever you do.