Webpack production mode tree shaking and dynamic module removal

Module optimization and dead-code elimination

Webpack uses the mode: 'production' setting to trigger internal presets, including the TerserPlugin, which performs dead-code elimination (tree shaking) to reduce bundle size. This process relies on static analysis to determine which exports are used across the dependency graph.

A conflict arises when modules contain functions that are invoked dynamically or through indirect references. While these modules are preserved in mode: 'development', the production optimizer may identify them as unused and remove them from the final output, leading to runtime errors in production environments.

The objective is to ensure specific modules are retained during the production build without disabling global minification or optimization settings.

• How should the sideEffects property in package.json be configured to exempt specific files or patterns from tree shaking?
• What is the recommended method to signal to the static analyzer that a module is required when a direct static import is not present?