Tree Shaking External Component Library?

[jpmarra]

Hey folks, quick question: I have an external component library that I'm including in my NextJS app as dependency. For some reason, it is not being properly tree-shaken. In the component lib, I have an esm module bundle ( pointed to the module field in pkgjson) and a cjs bundle (pointed to the main field in pkgjson). Anytime a component is included in a bundle in the NextJS app, it brings along all other unused components. Does anyone have an idea as to what the issue may be? Do I need to tell webpack to specifically use the module field for this package (per #9323) ?