# Additional features to \`import \* as Object from 'module'\`

**URL:** <https://es.discourse.group/t/additional-features-to-import-as-object-from-module/1164>\
**Category:** 💡 Ideas\
**Tags:** proposal\
**Created:** [January 21, 2022, 3:22pm UTC](https://es.discourse.group/t/additional-features-to-import-as-object-from-module/1164 "2022-01-21T15:22:53Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ljharb](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/ljharb/32/8_2.png) [@ljharb](https://es.discourse.group/u/ljharb)\
**Post date:** [January 21, 2022, 8:55pm UTC](https://es.discourse.group/t/additional-features-to-import-as-object-from-module/1164/3 "2022-01-21T20:55:58Z")

</div>

Treeshaking only provides a benefit when you import more than you need - which can only happen when you export more than you should.

If only "some" of a module might be needed at a time, imo it belongs in a different module - ie, in another file. Deep imports obviate the need for treeshaking, and make for much smaller application footprints and bundle sizes.

---

_[View the full topic](https://es.discourse.group/t/additional-features-to-import-as-object-from-module/1164)._