Modern JavaScript

Protect the JavaScript your current build already produces.

TypeScript, JSX, framework templates, and modern modules should be compiled first. JavaScript Obfuscator then protects the generated JavaScript files before they are deployed.

Build Workflow Guide Exclusion Rules
Compatibility Pattern

Compile first. Obfuscate second. Test the protected output.

This keeps JavaScript Obfuscator out of your framework compiler and makes protection a clear post-build step.

Framework safeProtect built JS instead of raw TypeScript, JSX, or single-file components.
Public API awareKeep exported or externally referenced names stable with exclusions.
Release friendlyRun after bundling and before upload, packaging, or deployment.
Framework Fit

Use JavaScript Obfuscator at the stable point in your pipeline

The safest integration is after your framework has produced normal JavaScript assets. That keeps source transforms, JSX compilation, tree-shaking, minification, and code splitting in the tools that already own them.

React and JSX

Build JSX into JavaScript first, then protect the generated chunks. Exclude names called by external scripts or server-rendered markup.

TypeScript

Run TypeScript compilation and type checking before obfuscation. Protect emitted JavaScript, not `.ts` source files.

Vue and Angular

Let the framework compiler generate runtime bundles first, then apply protection to the emitted JavaScript files.

Node.js output

Protect server-distributed JavaScript when source visibility is a risk, then test startup, dynamic imports, and runtime configuration paths.

Recommended order
npm run test
npm run build
javascript-obfuscator-desktop-cli project.jso
npm run smoke:protected
deploy ./dist-protected
Keep Names Stable

Protect private logic, preserve integration contracts.

  • Exclude global callbacks used by HTML attributes, analytics tags, or third-party widgets.
  • Preserve public method names that server templates, plugins, or external scripts call directly.
  • Use cross-file options when multiple generated files must agree on shared renamed symbols.
  • Test source maps, error monitoring, and stack traces according to your release policy.
Proof Points

What changed to close the modern JavaScript gap

Clear post-build guidance

The site now explains exactly where protection belongs for TypeScript, JSX, and framework-generated bundles.

Exclusion-first compatibility

Docs now point buyers to the public-name preservation workflow that prevents accidental API breakage.

CI path made visible

The build integration page gives teams a concrete release pattern instead of leaving automation implied.