Jscrambler Client for Browser and Node.js
DISCLAIMER: If you are looking for Jscrambler 3.8 or below please go to this page.
On your project:
npm i jscrambler --save-dev
Or globally:
npm i -g jscrambler
You may put your access and secret keys into a config file if found in these directories. Besides simplifying the command entry, this has the added benefit of not logging your Jscrambler credentials.
Here's an example of what your .jscramblerrc file should look like:
{
"keys": {
"accessKey": "AAAA",
"secretKey": "SSSS"
},
"applicationId": "XXXXX",
"filesSrc": [
"/path/to/src.html",
"/path/to/src.js"
],
"filesDest": "/path/to/destDir/",
"params": [
{
"name": "stringSplitting",
"options": {
"chunk": 1
}
}
],
"areSubscribersOrdered": false
}Please, replace the AAAA, SSSS and XXXXX placeholders with your API credentials and Application ID.
You can also download this file through Jscrambler's application builder. More information can be found here.
npm install -g jscrambler
Usage: jscrambler [options] <file ...>
Options:
-h, --help output usage information
-V, --version output the version number
-a, --access-key <accessKey> Access key
-c, --config <config> JScrambler configuration options
-H, --host <host> Hostname
-i, --application-id <id> Application ID
-o, --output-dir <dir> Output directory
-p, --port <port> Port
-C, --cwd <dir> Current Working Directory
-s, --secret-key <secretKey> Secret key
-R, --randomization-seed <seed> Set randomization seed
--recommended-order Use recommended order
-W --werror Cancel protection if any file contains errors
When making API requests you must pass valid secret and access keys, through the command line or by having a .jscramblerrc file. These keys are each 40 characters long, alpha numeric strings, and uppercase. You can find them in your jscramber web dashboard under My Profile > API Credentials. In the examples these are shortened to AAAA and SSSS for the sake of readability.
Jscrambler by default will protect your application even if errors occurred in some of your files. For example: if your app have 5 files and 1 of them has syntax errors, Jscrambler will protect the files with no errors and keep the original content in the other one.
With this flag, any error/warning will make the protection fail. There are two possible types of errors:
-
Syntax errors
Code
function a[] { return }
Output
Error: "Unexpected token [" in test.js:1 Protection failed -
Errors parsing jscrambler code annotations
Code
//@jscrambler define __something function test() { return true; } test(); //@jscrambler [define xxxxx] function test1() { return false; } test1();
Output
Error: "[Annotation Error] Expected " " or [a-z]i but "_" found." in test.js:1 Error: "[Annotation Error] Expected " ", "define", "disable", "enable", "global", "order" or "target" but "[" found." in test.js:8 Error: "Parsing errors on annotations" in test.js Protection failed
jscrambler -a AAAA -s SSSS -i APP_ID -o output.js input.js
jscrambler -a AAAA -s SSSS -i APP_ID -o output/ input1.js input2.js
jscrambler -a AAAA -s SSSS -i APP_ID -o output/ "lib/**/*.js"jscrambler -c config.json
where config.json is an object optionally containing any of the JScrambler options listed here, using the structure described in the RC configuration.
npm install jscrambler
var jscrambler = require('jscrambler').default; jscrambler.protectAndDownload({ keys: { accessKey: 'YOUR_JSCRAMBLER_ACCESS_KEY', secretKey: 'YOUR_JSCRAMBLER_SECRET_KEY' }, host: 'api4.jscrambler.com', port: 443, applicationId: 'YOUR_APPLICATION_ID', filesSrc: [ '/path/to/src/*.html', '/path/to/src/*.js' ], filesDest: '/path/to/destDir/', params: { stringSplitting: { chunk: 1 } } }) .then(function () { console.log('All done!'); }) .catch(function () { console.error('Something went wrong...'); });
More detailed informations can be found here.
Please refer to docs for more information.