ES3 File Converter

Purpose & User Intent: The es3 file converter addresses the need to port modern JavaScript to ES3-compatible syntax for legacy environments. It targets frontend engineers, maintenance teams, and build pipelines responsible for aging codebases. When deployments must run in older runtimes that lack ES6+ features, automated transformations provide a safe path to compatibility. Core capabilities include AST-based parsing, transformation passes, and ES3 code generation, with basic validation and reporting. For teams, this reduces risk and accelerates porting cycles.

Core Logic & Features: Required features include an AST-based parser, a sequence of transformation passes, ES3-ready code generation, and basic input validation with a change report. Optional features cover batch processing, per-file reports, source maps, comment preservation, and module-system adaptation (e.g., modules to IIFE). The tool assumes input is valid JavaScript and aims to preserve semantics while removing ES6+ constructs. It does not act as a full TypeScript/Flow transpiler or inject polyfills by default.

Inputs & Outputs: Inputs accept a JavaScript source file (.js) and optional settings such as target_version (ES3), preserve_comments, source_maps, and module_system. Outputs provide an ES3-compatible code file, processing status, and a per-file transformation report.

Algorithms & Calculations: The tool applies an AST-driven pipeline: normalize syntax, convert let/const to var, convert arrow functions to function expressions, replace template literals with string concatenations, emulate default/rest parameters, and adapt modules to IIFE or the selected system. It strives to preserve behavior, signaling potentially unsafe patterns.

Error & Edge Cases: Unsupported syntax (dynamic imports, heavy metaprogramming) may yield partial results or require manual intervention. Syntax errors halt processing with diagnostics. Large codebases can be processed in batches with per-file logs to isolate issues.

Industry/Region & Localization: Targets ECMAScript 3 compatibility for global web development; locale or regional formatting is not a factor. Standards relevant to this tool are ES3 compatibility and legacy browser support.

Assumptions & Exclusions: Input is JavaScript source; TypeScript/Flow features are not converted. No automatic polyfills unless configured. Not all ES6+ patterns have automatic equivalents in ES3; verify with your test suite.