We recently updated our module export from index.js to index.mjs at v4.3.6 to get better ESM support in Node env but we notice that there is an unreasonable size bump for the package on BundlePhobia. As you can see below, the package size of v4.3.6 is almost 2x the size of previous versions. To clarify, we did not add any dependencies or new entry points. We just updated the file extension from .js to .mjs.
To Reproduce
We published the same source to a node-esm tag but changing the module export extension back to .js. The package size then on BundlePhobia looks normal.
Therefore, we think BundlePhobia has trouble handling .mjs files and cannot calculate the right package size for module export using .mjs extension. If you need more info from us, feel free to contact or visit @aws-amplify/ui-react
Expected behavior
BundlePhobia should calculate the right size for ESM export using .mjs extension without double/triple counting its dependencies and the entire package size bump should be minor.
Package name
@aws-amplify/ui-reactDescribe the bug
We recently updated our
moduleexport fromindex.jstoindex.mjsatv4.3.6to get better ESM support in Node env but we notice that there is an unreasonable size bump for the package on BundlePhobia. As you can see below, the package size ofv4.3.6is almost 2x the size of previous versions. To clarify, we did not add any dependencies or new entry points. We just updated the file extension from.jsto.mjs.To Reproduce
We published the same source to a
node-esmtag but changing themoduleexport extension back to.js. The package size then on BundlePhobia looks normal.Therefore, we think BundlePhobia has trouble handling
.mjsfiles and cannot calculate the right package size formoduleexport using.mjsextension. If you need more info from us, feel free to contact or visit@aws-amplify/ui-reactExpected behavior
BundlePhobia should calculate the right size for ESM export using
.mjsextension without double/triple counting its dependencies and the entire package size bump should be minor.