"This repo aims to get you up and running with sane defauts. Most of the content is in the 'both' folder so that we can so serverside rendering more easily."

No "both" folder available after running. Did this change?

Hi Adam,

great boilerplate here! I have been using the blaze-react-component module too for loginButtons but this gets to be a problem as you start applying any sort of styling on to the app as the loginButtons don't change from their "Blazey" look. In particular I am interested in having a "bootstrappy" look for my loginButtons. Do you know if a React-style version of loginButtons exists or any interest in creating one?

thanks!
Shawn

I posted this question on SO after watching your VIDEOS series in which you were using FlowRouter with react router. However, this repo migrated to rr4 and I am trying to get a redirect onSubmit but it doesnt seem to work.
Route redirects are working fine, as in user cannot access register/login when already loggedin, but when on the login page, user is not redirected.
There isnt a FlowRouter.go() equivalent in rr4 and I am forced to put the login check logic within the component and force rerender with react's this.forceUpdate() - which doesn work for me
here is the SO question

Hi Adam,

Thanks for this. Whilst I've used Meteor before, this is my first time using React + Meteor. This boilerplate has generally been quiet useful to get started quickly, with just enough examples on the way through to see where to go.

I have a question about the use of Browserify and server side rendering...

Components are defined on both the server and client, which makes sense to allow server side rendering (although I'm not using that currently), but browserify only installs react-components on the client, since its defined in client/lib/. This caused an error on the server, since the react-components did not exist there.

My particular use case is trying to get the React Drop and Drag module set up.

[client/lib/app.browserify.js]

DragDropContext = require('react-dnd').DragDropContext; 
HTML5Backend = require('react-dnd-html5-backend');

Then wrap the MainLayout component in the higher-level DragDropContext (as per their instructions).

[both/pages/MainLayout.jsx]

 MainLayout = DragDropContext(HTML5Backend)(MainLayout);

The server throws an error the 'HTML5Backend' is not defined.

Moving these component definitions inside client/ seems to have worked though.

Have I totally missed something?

Thanks

Hi, I like your boilerplace very much.
Could you please update to meteor 1.4?