tc39/proposal-export-default-from

Still stage 1?

Opened this issue · 13 comments

stevenvachon commented

What can be done to move this forward? I think it's important.

mesqueeb commented

Oh wow, I also thought that this only missing way of re-exporting a default export was a bug in babel. Until it lead me here!!
Does stage 1 mean it's still far from being added or already close?

obedm503 commented

See https://tc39.es/process-document/ for an explanation of the process.

mesqueeb commented

In order to make this stage 2, we need to:

Precisely describe the syntax and semantics using formal spec language

@leebyron
@jdalton

is any of you willing to do this? I think this is what is holding this back to go to stage 2.

  • 👍1
rob2d commented

@mesqueeb is this open to anyone for contribution? I find this pretty important for succinctness in my projects -- not to mention not relying auto-generator for export * as default from './my-modules'. May take a shot if so (apologies if this is a really basic/uninformed question btw).

  • 👍1
ljharb commented

It's still stage 1; anyone is certainly welcome to submit a PR that includes full ecmarkup-compliant spec text - but to set expectations appropriately, a TC39 champion would have to both be active and then to review the PR.

However, if a PR existed that actually completed all the prerequisite work required to make this proposal eligible for stage 2, then the likelihood that a TC39 member would decide to become a champion goes up tremendously.

  • 👍2
mAAdhaTTah commented

@ljharb Is this feasible as a consensus PR, the way export * as ns from was?

ljharb commented

No, the committee already decided this must be a proposal.

stevenvachon commented

What is involved for someone to champion this? I've never done it and might be interested.

  • 👍1
ljharb commented

@stevenvachon only TC39 delegates are eligible to be champions.

mesqueeb commented

How to become delegate ?