James Friend

Official JSX doesn't support comments and I'm not particularly inclined to add `` to CJSX because they would have to be special-cased in the parser.

That wouldn't really make sense. Hash-comments go to the end of the line, so how would we differentiate a curly bracket which is just part of the comment from one...

Interesting. I'm in favour of implementing comments with the same semantics as JSX

This is a consequence of how loose/dumb the parser is. I'm currently experimenting with a new implementation which would tighten up to the CJSX grammar a bit, in a way...

No timeline on the new parser as yet. The current compiler could be made to fail if something which looks like a tag was detected in a CJSX 'text node',...

Oh, is it a maximum open files issue? What OS are you on? Have you tried increasing the operating system's `ulimit`?

@joshfrench Just realised this was related to https://github.com/jsdf/browserify-incremental/issues/7 as the specific version of browserify which is bundled with browserify-incremental has this issue, but a later version seems to have fixed...

coffee-react-transform won't be any different to normal coffeescript. I'm not sure how the Meteor modules support works, but basically you need to figure out what ES5 javascript code Meteor converts...

coffee-react-transform will leave these statements untouched. coffee-script will also just pass them straight through. What will process the es6 import syntax? No browser supports it natively yet. Have you configured...

:+1: