[treeshaking]: fix treeshaking and add esm and umd versions #1045
Conversation
davidicus
requested review from
blechner,
bryancboyd,
cgirani,
filipecorrea,
jessieyan,
leetosc,
scottdickerson,
sstone2423,
stuckless,
tay1orjones and
tomklapiscak
as code owners
|
Deploy preview for carbon-addons-iot-react ready! Built with commit 64f8d53 https://deploy-preview-1045--carbon-addons-iot-react.netlify.com |
I believe this is the case because of the preserve modules flag. We can only dictate a directory with this property set to true but luckily we tell consuming apps where to find the entry point and all paths like ones used for styles are still valid. |
…eact into tree-shake-build
|
🎉 This PR is included in version 2.61.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
after adding changes to CLI to add d3 as dep for our esm module version we can see that d3 is still not shipped with the application |
Closes #993 closes #1011
Summary
Changes to our build to allow for es and umd versions and to allow for treeshaking in consuming applications.
Change List (commits, features, bugs, etc)
Acceptance Test (how to verify the PR)
yarn build should output a lib, es, umd, and scss folder.
Using the
create-iot-react-appcli I was able to test the baseline build. Like the issue opened on this reports the original build was around2.74 MB. With tree shaking and dead code elimination this new build is now able to deliver the same app in under314 KBwhich is around an 88.5% savings.