tc39 / tc39/proposal-export-star-default
export default from
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
The slides mention that:
export {default} from 'some-module-without-default'results in an error, preventing generic proxy modules- https://github.com/tc39/proposal-export-default-from is stuck at stage 1.
If the semantics of export default from 'some-module' was to only export a default if the module exports it, would it solve the use case? The main difference with the export ** approach is that you'd have to remain explicit on which module the default is from instead of the magic "the one of the multiple 'export from' that defines it"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with issue #2 and the linked TC39 export-default-from proposal. Compare the proposed conditional export default from semantics with the existing export * behavior and the stated generic proxy-module use case. Done means the proposal's semantics and compatibility implications are clearly resolved, not just discussed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100