esnext / es6-module-transpiler

Tomorrow’s JavaScript module syntax today

http://esnext.github.io/es6-module-transpiler/

Other

1.21k stars 85 forks source link

Remove warning about ES6 module format churn #166

Closed trek closed 9 years ago

trek commented 10 years ago

barring anything O_O it should be finalized as of July.

caridy commented 10 years ago

-1

we are almost there, you can follow the progress here: https://github.com/esnext/es6-module-transpiler/issues/162

trek commented 10 years ago

162 is similar but unrelated.

This PR doesn't remove language that es6-module-transpiler currently only supports a subset of ES6 module syntax. It removes references to the official spec not being finalized.

caridy commented 10 years ago

that's what #162 is doing, making sure that this tool follows the final specs :), not a subset, and yes, grammar wise, we are NOT planning any change (I should probably say: we are NOT GOING to consider any changes to the spec at this point).

once #162 is solved, we can clean this up.

trek commented 9 years ago

162 will remove the "subset" part, yes. But the spec is finalized. The README still says it is not, and people are pointing to the README and saying "I don't think the spec is finalized". That's what this PR addresses.

caridy commented 9 years ago

we merged https://github.com/esnext/es6-module-transpiler/pull/167 yesterday, we are getting close to get the stars aligned, then we can revisit this one.

trek commented 9 years ago

That will require a different PR though. Both removing references to the spec not being finalized (which is mergeable today) and rewording the warning about the transpiler not supporting the full spec (which depends on #167)