lodash vs lodash-es for bundle optimization

A small-scale application currently utilizes the full lodash package. To reduce the production bundle size, there is a need to transition to a more modular import strategy. The primary goal is to minimize the JavaScript payload without introducing runtime regressions or duplicate utility instances.

Two documented approaches exist: importing specific methods from the CommonJS lodash package (e.g., import debounce from 'lodash/debounce') or migrating to the lodash-es package to leverage native ES module tree-shaking via build tools like Webpack or Rollup.

The uncertainty lies in the potential for bundle duplication if both formats are accidentally mixed during a phased migration, and whether certain complex methods maintain identical behavior across these different distribution formats.

• Does lodash-es provide a significant size advantage over cherry-picked lodash imports in modern build pipelines?
• What are the risks of mixing these two packages during an incremental migration?