Many people are interested to the Meteor + React combo for many reasons, but currently I see many options to build the “initial puzzle”, so I start this thread to hear your opinion.
Some “moving parts” come from Meteor some other come from React, however it would be more difficult to share a generic high level component (e.g meteor-react-account-ui) if we use completly different “bricks”.
NOTE: I didn’t mention all the possible combination of the ingredients you can use to cook your Meteor + React soup. So feel free to add yours
ES2015 import/export modules
WHY: to control the load order of your js files in your app
The upcoming Meteor 1.2 will support ES2015 by default via Babel but not the modules.
- webpack + react + meteor https://github.com/jedwards1211/meteor-webpack-react
- universe:modules https://github.com/vazco/universe-modules/
Router client + server SSR
WHY: because also a SPA needs different routes with different components
WHY: because mostly react components shouldn’t depend on the Meteor persistence layer (Minimongo)
WHY: you can DIY, but an UI with theme support and many base component is a good start that you can alwais override later
WHY: because good components are bit configurable and support i18n
- tap:i18n (seems Blaze specific)
Have you already made some stable choice or will you continue to choose this “components” on per app basis?