export-ns-from (Needs Consensus PR)
- Dominant language
- No language data
- Stars
- 435
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Champions: @jdalton @benjamn (prev @leebyron)
Spec Repo: https://github.com/leebyron/ecmascript-export-ns-from
Moved to Stage 2 at the July 2017 meeting: https://github.com/tc39/agendas/blob/master/2017/07.md
Approved as a needs consensus PR at Sept 2017 meeting (Stage 4) (https://github.com/tc39/ecma262/pull/1005)
Syntax
```js
export * as ns from 'mod';
```
## Implementation
- [x] Already implemented in https://babeljs.io/docs/plugins/transform-export-extensions/ but we should split it out
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with Babel's documented transform-export-extensions plugin and compare its existing export * as ns from 'mod' implementation with the linked ECMAScript proposal. The change is done when this functionality is split into its own implementation while preserving the specified syntax; the issue names no source file or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- babel, javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100