docx VS javascript-obfuscator

Since I don't have much knowledge of web development, the application has a very basic structure: html + css + javascript. To generate the document, I use a library called docx.js (https://docx.js.org). When the user clicks to submit the form, the request is passed to a function in the main file (app.js), which , through conditional logic, assembles the document using docx.js.

Looks like this library wasn't meant to open existing files: https://github.com/dolanmiu/docx/issues/1513

Had such requirement in the past, this worked well https://docx.js.org/

Honestly with this brief I'd avoid Ruby/Python and go straight with JavaScript. UIs with javascript are pretty easy, and there are great libraries out there like https://github.com/dolanmiu/docx which make it relatively easy to edit word documents.

For Excel it's much easier to convert your raw data to CSV than to put it into an HTML document and then extract it back out again. Similarly for .docx format, you're probably better off using a package like docx and building the document in a way more suited to the file format than trying to smush HTML into a new format.

I don't need/use IDA, Nemlei just used https://obfuscator.io/, which just obfuscates the crap out of the code using various known methods (which I won't go into detail, it's public knowledge) and an un-obfuscation was cooked up by others. The one fucked-up thing the website does is randomizing function names, it just changes every variable/function name. We can't "un-obfuscate" those, so it's up to our brains to figure out what the code does, and change the names back.

I was considering using a obfuscation library (https://github.com/javascript-obfuscator/javascript-obfuscator) and noticed in the usage example that backticks are used and the javascript is enclosed within. The issue is that my javascript already has backticks from using template literals so my code then errors out.

Obfuscation: JavaScript Obfuscator

What I ended up doing is having two build steps, one for renderer and other for the main process, in the main process build I use https://github.com/javascript-obfuscator/javascript-obfuscator. Works pretty fine.

It's to purposefully makes your code harder to read so it prevents people from stealing your work. Here's a tool that does it: https://obfuscator.io/

I just tested it on a little snippet of my code obfuscated with https://obfuscator.io/ and it worked seemingly perfectly.

My original code:

  function resizeImage(img) {

https://obfuscator.io/ produces a similar result, perhaps that's all they used.