Tree-shaking enabled and verified

When tree-shaking is disabled or ineffective, every utility your bundler pulls in ships in full — including the 95% of lodash or date-fns that your code never calls. On a typical project that imports from 10–15 large libraries, inactive tree-shaking can add 200–400KB of dead code to the production bundle. ISO 25010:2011 resource-utilisation captures the storage and bandwidth waste; the user-facing cost is slower parse and execution time on every visit.

Switch to ES module named imports for every large dependency and ensure your build runs in production mode. Add "sideEffects": false to your own package.json so downstream bundlers can tree-shake your code too.

// Before (imports all of lodash)
import _ from 'lodash'

// After (tree-shakeable — only debounce bundled)
import { debounce } from 'lodash-es'

In package.json, add:

{ "sideEffects": false }