Socket
Socket
Sign inDemoInstall

nextjs-obfuscator

Package Overview
Dependencies
200
Maintainers
1
Versions
10
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

    nextjs-obfuscator

javascript obfuscator plugin for next.js


Version published
Weekly downloads
702
decreased by-3.44%
Maintainers
1
Install size
908 kB
Created
Weekly downloads
 

Readme

Source

javascript-obfuscator plugin for Next.js

npm

The nextjs-obfuscator enables you to make your Next.js app difficult to be reverse-engineered, using javascript-obfuscator.

ℹ️ If you are looking for README for v1, see here.

There are some useful notes:

  • The app router is supported.
  • Building by turbopack is currently NOT supported.
  • Minimum supported Next.js version is v13.

Installation

You have to install javascript-obfuscator separately.

On npm:

npm i -D javascript-obfuscator nextjs-obfuscator

On yarn:

yarn add -D javascript-obfuscator nextjs-obfuscator

Usage

Wrap your configuration in your next.config.js to use this plugin, for example:

const withNextJsObfuscator = require("nextjs-obfuscator")(obfuscatorOptions, pluginOptions);

/** @type {import('next').NextConfig} */
const nextConfig = withNextJsObfuscator({
  // ... your next.js configuration
});

module.exports = nextConfig;

If you use some other plugins, we recommend applying this plugin later than any other ones because in most cases the obfuscation will change a large portion of the code.

API

require("nextjs-obfuscator")(obfuscatorOptions, pluginOptions)

obfuscatorOptions

Type: Object (required)
This is the options of javascript-obfuscator, but there are some important notes:

pluginOptions

Type: Object (optional)
More options for this plugin. All properties are optional.

{
  enabled: boolean | "detect",
  patterns: string[],
  obfuscateFiles: Partial<{
    buildManifest: boolean,
    ssgManifest: boolean,
    webpack: boolean,
    additionalModules: string[],
  }>,
  log: boolean,
};
OptionTypeDefault ValueDescription
enabledboolean | "detect""detect"Indicates if the plugin is enabled or not.
If "detect" specified, the plugin will be enabled only when building for production.
patternsstring[]["./**/*.(js|jsx|ts|tsx)"]Glob patterns to determine which files to be obfuscated. They must be relative paths from the directory where next.config.js is placed.
obfuscateFilesobjectAdditional files to be obfuscated.
obfuscateFiles.buildManifestbooleanfalseIf set to true, the plugin will obfuscate _buildManifest.js
obfuscateFiles.ssgManifestbooleanfalseIf set to true, the plugin will obfuscate _ssgManifest.js
obfuscateFiles.webpackbooleanfalseIf set to true, the plugin will obfuscate webpack.js, which is an entry point.
obfuscateFiles.additionalModulesstring[][]Names of additional external modules to be obfuscated. Convenient if you are using custom npm package, for instance. Use like ["module-a", "module-b", ...].
logbooleanfalseIf set to true, the plugin will use console.log as logger. Otherwise, it uses webpack's standard logger.

How it works

  • This plugin inserts a custom loader to obfuscate project files and external modules.
  • This plugin inserts a custom plugin to obfuscate buildManifest, ssgManifest, webpack assets.

Disclaimer

Using this plugin can break your next.js app, so you have to check carefully your app works fine.

License

LICENSE

Keywords

FAQs

Last updated on 20 Nov 2023

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc