4 ms·
One of the things still holding me back from using Meteor with React is the lack of support for a module loading system. It seems like if I want to define a co
by gmaster1440 11y ago
One of the things still holding me back from using Meteor with React is the lack of support for a module loading system.
It seems like if I want to define a component in a separate file, I'll have to assign it to a global variable if I'm going to compose it in another file.
- mquandalle 11y agoUsing global variables isn’t even the worst part. The big problem with this sharing model is that files are loaded in the alphabetical order, thus the only way to control that file a requires file b as a dependency is to give to b a file name that is before a in the alphabet (this is not true for Meteor packages where we can control the file order). Thankfully MDG plan to address this issue soon.
- gmaster1440 11y agoYeah, good to know.
- rralian 11y agoI agree, but this is why I was very excited when I found this skeleton project. https://github.com/jedwards1211/meteor-webpack-react https://github.com/jedwards1211/meteor-webpack-react It should give you the modules and full es2015 you're looking for.
- bvm 11y agoTagging on to this, I assume we can't use all of ES2015 classes with react and meteor, as the mongo bit requires mixins. Is there a fix in the works for this?