You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, but the source maps don't need to be public. With tools such as Sentry you can have private source maps. The way it works is that you upload your source maps to Sentry and the logged exceptions are mapped to the original code instead of the obfuscated one.
Base realisation in master branch, but 0.7.0 will be ready only when i write tests for all node obfuscators.
Look at readme update for new method obfuscateWithSourceMaps and CLI usage
Activity
sanex3339 commentedon Jul 7, 2016
I haven't see no point to even looking into source maps direction, because main goal of obfuscated code is to hide source code.
nickdima commentedon Jul 7, 2016
The point would be for tracking errors in production.
sanex3339 commentedon Jul 7, 2016
As i sayd before, with source maps anyone can see all obfuscated code as source code.
You can disable obfuscation for debugging.
nickdima commentedon Jul 7, 2016
Yes, but the source maps don't need to be public. With tools such as Sentry you can have private source maps. The way it works is that you upload your source maps to Sentry and the logged exceptions are mapped to the original code instead of the obfuscated one.
sanex3339 commentedon Jul 7, 2016
I will try to do that, but can not guarantee
nickdima commentedon Jul 7, 2016
Thanks!
sanex3339 commentedon Jul 7, 2016
Did it. Will be ready with 0.7.0
nickdima commentedon Jul 7, 2016
Wow! Awesome!
sanex3339 commentedon Jul 9, 2016
Base realisation in master branch, but 0.7.0 will be ready only when i write tests for all node obfuscators.
Look at readme update for new method
obfuscateWithSourceMapsand CLI usagelock commentedon Jun 6, 2018
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.