Closed shadowmint closed 9 years ago
+1 just stumbled across this little tid bit as well.
That is actually a proposed ES7 feature (see http://facebook.github.io/react/docs/transferring-props.html#rest-and-spread-properties-... ) that react seems to endorse.
You probably need to add reactify (https://www.npmjs.com/package/reactify) to your toolchain when building.
@treo The errors above are running gulp in the example directory, which uses reactify.
If some specific reactify config is required, could we at least get the example updated to use it?
On Wednesday, March 11, 2015, treo notifications@github.com wrote:
That is actually a proposed ES7 feature (see http://facebook.github.io/react/docs/transferring-props.html#rest-and-spread-properties-... ) that react seems to endorse.
You probably need to add reactify (https://www.npmjs.com/package/reactify) to your toolchain when building.
— Reply to this email directly or view it on GitHub https://github.com/callemall/material-ui/issues/392#issuecomment-78256607 .
NOTE:
In the example below, the --harmony flag is required as this syntax is an experimental ES7
syntax. If using the in-browser JSX transformer, simply open your script with
<script type="text/jsx;harmony=true">.
You must use the --harmony flag with reactify for this to work.
I can currently build the project. Can you please have a look into the problem and close this issue if not applicable anymore?
This should be fixed with #656, @shadowmint can you please pull down the latest master to verify this?
Fixed with #656
The use of ES6 proxies has broken everything.
Trying to build the example results in:
Specifically, this is due to the use of:
What's the plan here?
Babel does not provide any polyfill for this, and browserify cannot parse it.