-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Absolute path as parameters #576
Comments
Hi. I can't test it on the |
Anyone can investigate this? |
maybe you can try |
Hi. Any news? |
I tried all the variants of slashes possible. The problem was still there, but i managed to found a workaround. I'll need this obfuscator soon enough to give you feedback concerning this problem / bug |
No, not slashes or backslashes cause this bug. First, i used to think that is because of exception in Then i added some Soooo: Expected result path: Actual result path: I think bug is in function |
This we have also faced. Has this been addressed? @sanex3339 |
PR welcomed. Also, i need a way to test this behaviour under UNIX environment, but I don't sure how to do that. |
Anybody can test this PR: |
Merged to the |
Released as |
Hi,
I don't understand why I call javascript-obfuscator with absolute path and it doesn't work. I call it like this:
javascript-obfuscator C:\NodeJsObfuscate\src --output C:\NodeJsObfuscate\obfuscated
I get the error: Illegal characters in path. When I pass absolute path a source files, the app get the source correctly and it works, but the absolute path for the --output parameters cause error. What am I doing wrong ?
Thanks in advance
The text was updated successfully, but these errors were encountered: