PJSD now has a new name, JSDefender, so we changed the pjsd-
prefix of the package names to jsdefender-
. There is also a new configuration file format, new protection transforms, and several other major changes since version 1.3. We have released an Upgrade Guide to help migration from PJSD 1.3 to JSDefender 2.0. We have also updated the full User Guide.
--constarg
, --constargoff
, --datelock
, --exprseq
, --exprseqoff
, --propsparsing
, --propsparsingoff
, --selfdefend
, --selfdefendoff
, --vargroup
, --vargroupoff
, --estarget
, --randomseed
, --ignore-unsafe
, and --disable-inline
.--inclusive
, -s/--scope
, --idprefix
, --id-map
, --id-map-in
, --id-map-out
, -a/- anns
, -A/- annsoff
, and --es5
.-m
,--mapout
option is turned on by default. You should use -m off
or --mapout off
to disable generating lexical maps.jsdefender.config.json
, unless an explicit configuration file is specified.constantArgument
, dateLock
, expressionSequence
, propertySparsing
, selfDefending
, and variableGrouping
.stringLiterals
and selfDefending
protection transforms for the modules within the bundle.@jsdefender
tag, though the obsolete @pjsd
tag can still be used.DomainLockTransform
now accepts multiple domain name patterns separated by semicolons.IntegerLiteralTransform
now has two new optional configuration settings, lower
, and upper
, to set the range of numeric literals to obfuscate.jsdefender.config.json
by default, just as the CLI does. You can set the name of the configuration file in the plugin options, if it has a different name or location.jsdefender.config.json
by default, just as the CLI does. You can set the name of the configuration file in the plugin options, if it has a different name or location.LocalDeclarationTransform
is fixed.IntegerLiteralTransform
bug with lower
and upper
values between 0x8000
and 0xffff
is fixed.