Jscrambler Webpack Plugin

This plugin protects your webpack output using Jscrambler.

Version Compatibility

The version's compatibility table match your Jscrambler Version with the Jscrambler Webpack Plugin. Please make sure you install the right version, otherwise some functionalities might not work properly.

Usage

Simply add the plugin to your configuration. We recommend placing it after every other plugin that also modifies your code. It will automatically gather all JavaScript and HTML files and protect them.

Example webpack.config.js:

const {resolve} = require('path');
const JscramblerWebpack = require('jscrambler-webpack-plugin');

module.exports = {
  mode: 'production',
  entry: {
    protected: './app/index.js',
    unprotected: './app/index.js'
  },
  output: {
    filename: 'dist/[name].js'
  },
  devtool: 'source-map',
  module: {
    rules: [
      {
        test: /\.js$/,
        exclude: /node_modules/,
        loader: 'babel-loader'
      }
    ]
  },
  plugins: [
    new JscramblerWebpack({
      enable: true, // OPTIONAL, defaults to true
      chunks: ['protected'], // OPTIONAL, defaults to all chunks
      ignoreFile: resolve(__dirname, '.jscramblerignore'), // OPTIONAL, defaults to no ignore file
      params: [], 
      obfuscationLevel: 'bundle', // OPTIONAL. Available options are: bundle (default) or module
      obfuscationHook: 'emit' // OPTIONAL. Available options are: emit (default) or processAssets  
      // and other jscrambler configurations
    })
  ]
};

The Jscrambler client will use .jscramblerrc as usual, though it is possible to override specific values using the plugin's configuration.

The ignoreFile option will tell Jscrambler the path to the .jscramblerignore file. You can find more informations and examples in Ignoring Files.

Additionally, you may specify which chunks to protect using the chunks property, which accepts an array with the names of the chunks you wish to protect.

Obfuscation level

You can obfuscation the entire bundle (default way) or the modules inside it. The latter option is required when the native APIs (or polyfills) are not available right at the beginning of the application runtime.

Early versions of NativeScript mobile framework (<= 6) are a good example of this behaviour, and in order to protect those NativeScript Applications with Jscrambler you must set obfuscationLevel to module.

Note: Ofuscation level module is not compatible with source maps.

Obfuscation Hook

There are some webpack plugins, such as webpack-subresources-integrity, that should run after the obfuscation step. If those plugin are taking advantage of the new processAssets compilation hook (available on webpack 5 and onwards) to perform their tasks, that creates an incompatibility with the jscrambler-webpack-plugin.

If your use case matches the one describe above, please set obfuscationHook: processAssets (Only for webpack >= 5)