Re: exports at the top of the file

> > ```js > export default myConst; > const myConst = {}; > ``` > would throw because when the export is evaluated Correct, if you wanted to export `myConst` as the default without that issue, you'd want to do ``` export {myConst as default}; const myConst = {}; ``` to declaratively expose the

exports at the top of the file

Douglas Crockford said that eventually JSLint would require exports at the top of the file. However I think there are some issues. If my understanding is correct, ```js export default myConst; const myConst = {}; ``` would throw because when the export is evaluated, in step 2 of the Evaluation

Re: A plan to help TC39 become more open up to community contributions and participations

Excuse my ignorance, but why do we need the legal organization, why to not simply do the GiHub part? On Fri, Jun 3, 2016 at 6:36 AM, G. Kay Lee < balancetraveller+es-disc...@gmail.com> wrote: > Hi Allen, thanks for extending your support :-D > > My observation as well as belief is that, if a