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
{{ message }}
This repository has been archived by the owner on May 25, 2020. It is now read-only.
It would be REALLY cool if node-obfuscator could generate source maps that link the obfuscated JavaScript code back to the appropriate source file/line/column, etc. for debugging purposes.
From what I understand, you could pass a source map option to node-obfuscator to eventually be passed along to uglifyjs; however, this source map would be for the concatenated JavaScript, not for the original source. With a little bit of work, it might be possible to map the uglifyjs source map back to the original source code.
Thoughts on this?
The text was updated successfully, but these errors were encountered:
Hmm.. may be able to add it in at obfuscator.register, as it's aware of both the filename and its contents. I like the idea, as it would make locating bugs much, much easier.
It would be REALLY cool if node-obfuscator could generate source maps that link the obfuscated JavaScript code back to the appropriate source file/line/column, etc. for debugging purposes.
From what I understand, you could pass a source map option to node-obfuscator to eventually be passed along to uglifyjs; however, this source map would be for the concatenated JavaScript, not for the original source. With a little bit of work, it might be possible to map the uglifyjs source map back to the original source code.
Thoughts on this?
The text was updated successfully, but these errors were encountered: