Closure Compiler能否保留函数参数名称？

Great question—this is exactly the kind of tweak you need when working with IIFE-based modules where parameter names are tied to critical module data references. Let’s break down the practical ways to configure Closure Compiler to keep those parameter names intact while still getting solid compression:

1. Global Command-Line Flag #

The simplest way to preserve parameter names across your entire codebase is to use the --preserve_param_names flag when running the compiler. This tells Closure Compiler to skip renaming function parameters, even when using aggressive optimization levels like ADVANCED_OPTIMIZATIONS.

Example command:

java -jar closure-compiler.jar --compilation_level ADVANCED_OPTIMIZATIONS --preserve_param_names --js your-module.js --js_output_file your-module.min.js

This works perfectly for IIFE modules, as it’ll keep the parameter names in your wrapper functions from being mangled, so you don’t lose the link between those parameters and the module data they reference.

2. Per-Function JSDoc Annotation #

If you only need to protect parameter names for specific IIFEs (and not every function in your code), use the @preserve JSDoc annotation directly on the target function. This lets you keep compression tight elsewhere while safeguarding the critical parameter names in your modules.

Example:

/**
 * @preserve
 */
(function(moduleConfig, utilsLib) {
  // Your module code that relies on these parameter names
})(appConfig, coreUtils);

For more granular control, you can also use @suppress {rename}, though @preserve is more straightforward for this exact use case.

3. Adjust Compilation Level (If Less Aggression Is Acceptable) #

If you don’t need the full power of ADVANCED_OPTIMIZATIONS, switching to SIMPLE_OPTIMIZATIONS will by default preserve parameter names. This level still handles basic minification (like stripping whitespace, shortening local variables) but avoids aggressive renaming of function parameters.

Just note that you’ll miss out on some of the deeper optimizations that come with ADVANCED_OPTIMIZATIONS, so this is a trade-off between compression intensity and parameter preservation.

Quick Tips #

• When using ADVANCED_OPTIMIZATIONS with --preserve_param_names, make sure your IIFE parameters aren’t flagged as unused. The compiler might still strip parameters it thinks aren’t being used, so double-check that your module actually references them.
• Avoid mixing --preserve_param_names with flags that override name preservation (like --rename_prefix_namespace) unless you’ve tested their interaction thoroughly.

内容的提问来源于stack exchange，提问作者optimalisatie