# Grouped Export Namespaces: \`export { foo, bar } as qux\`

**URL:** <https://es.discourse.group/t/grouped-export-namespaces-export-foo-bar-as-qux/2327>\
**Category:** 💡 Ideas\
**Tags:** proposal\
**Created:** [March 23, 2025, 9:35am UTC](https://es.discourse.group/t/grouped-export-namespaces-export-foo-bar-as-qux/2327 "2025-03-23T09:35:05Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [March 24, 2025, 3:59am UTC](https://es.discourse.group/t/grouped-export-namespaces-export-foo-bar-as-qux/2327/4 "2025-03-24T03:59:47Z")

</div>

Binding semantics are governed by the spec - nothing loses track of them.

Typically tests and/or types are how you avoid refactoring hazards.

`import * as` is only for laziness or metaprogramming, and i’m not sure why it’d be a benefit to encourage either.

---

_[View the full topic](https://es.discourse.group/t/grouped-export-namespaces-export-foo-bar-as-qux/2327)._