Why we need optimizePackageImports in the Presence of Tree Shaking
Unanswered
Jersey Wooly posted this in #help-forum
Jersey WoolyOP
Hello guys, I've been reading about the optimizePackageImports option in Next.js (https://nextjs.org/docs/app/api-reference/next-config-js/optimizePackageImports) and I'm trying to understand its purpose. The documentation states that adding a package to experimental.optimizePackageImports will only load the modules you are actually using within a package and not things ur not using. However, isn't this what tree shaking is supposed to do? Why would we need this option if we already have tree shaking in our bundler? What are the specific use cases or scenarios where optimizePackageImports would be beneficial over traditional tree shaking?