Bug: The API fails if the filesSrc contains only a single file

[skilledDeveloper]

options.filesSrc accepts an array of strings but if you pass a single filename like the following it will fail:

options.filesSrc = ["file1.js"]

The problem is not with the obfuscation process. It happens after that when it tried to write the file in the output directory:

 Error: EISDIR: illegal operation on a directory, open 'OUTOUT_DIR'

Workaround: Adding another file in the filesSrc will fix the issue.

[luisreis-jscr]

Hello. The issue here is that when the project has only a single file, Jscrambler outputs a file instead of outputting a directory.

Is this causing you problems?

[skilledDeveloper]

Yes. That’s the issue.
If this is the intended behavior, it’s very inconsistent and needs to be changed IMO. In the config, you usually specify an output directory. Regardless of how many files you processed, the result should be sitting there in the output dir.

[luisreis-jscr]

There is a way to turn off this behavior: if you make the filesDest field end in a "/" or "\", it will always output a folder, even if only one single file was protected.

Example: options.filesDest = "dist/";