Feat/exclude file setting #28
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
While you're reviewing the updates, I've also published them on NPM. To install the latest version, use: yarn add -D @attarchi/obfuscator-io-metro-plugin |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added an "exclude" option for JavaScript obfuscation.
README.md: Updated documentation to include the new
excludesoption.lib/javascriptObfuscatorAPI.js: Integrated logic to allow specific files or patterns to be excluded from obfuscation based on
runConfig.excludes. Files matching the specified glob patterns will be omitted, enhancing customization and control over obfuscation.This improvement is useful for cases where certain assets should remain unobfuscated, facilitating easier debugging or performance optimizations in specific modules.