JavaScript Code Optimizer

Purpose & User Intent: The tool solves the problem of producing faster, smaller JavaScript code by applying safe static transformations and selective minification. Target users include frontend and Node.js developers, build engineers, and performance auditors who require repeatable, auditable optimizations during development or pre-release cycles. Users provide source code and optional environment targets to obtain an optimized variant and a measurement report.

Core Logic & Features: The tool performs AST-based analysis and pattern-driven rewrites with deterministic outcomes that preserve runtime behavior. Required features include syntax parsing, safe transformations, and reproducible optimization passes. Optional/advanced features include aggressive inlining, cross-file dead code elimination, tree-shaking, scope hoisting, and module-aware polyfill pruning. It supports both ES modules and CommonJS and can target browser or Node environments.

Inputs & Outputs: Inputs include code (string, required), target_env (browser|node, optional), es_version (e.g., ES2020, optional), optimization_level (safe|balanced|aggressive, optional). Outputs provide optimized_code (string) and metrics (object) containing size_reduction_percent, perf_improvement_percent, and analysis_time_ms.

Algorithms & Calculations: Transformations rely on AST traversal, reference counting, and pattern databases to select safe optimizations. The tool estimates gains using static heuristics and lightweight micro-benchmarks on representative patterns, without executing the target code. Results include the transformed code and a quantitative estimate of size and speed improvements, plus a safety flag for each change.

Error & Edge Cases: Handles syntax errors gracefully; for code with dynamic features, unsupported syntax, or runtime dependencies, it flags the issue and restrains optimizations to safe subsets. If external modules or dynamic imports inhibit cross-module analysis, the tool de-risks changes and reports conservative results.

Industry/Region & Localization: Aligns with ECMAScript standards up to the specified es_version and supports CommonJS and ESM. Outputs and reports use neutral, English-language terminology suitable for global engineering teams; no currency or locale-specific adjustments are applied to code semantics.

Assumptions & Exclusions: Assumes input code is intended to run in a compatible environment and that side effects are observable to the analysis tool. Excludes runtime instrumentation, full bundling, framework-specific transforms, and non-JS assets. The tool does not guarantee performance improvements in all cases and should be validated in a real test suite.