Closed hillscottc closed 7 years ago
Hmm. Looks like the multiple Invariant Violation: Element type is invalid: expected a string (for built-in components) or a class...
are being thrown by the LazyRoutes being passed to the router.
You know, what I like the best about this boilerplate is the clean webpack 2 config with React + Mobx. I am less enthusiastic about a new take on react-routing, if that is what's tricky.
Try pulling now, I've updated to the latest React Router 4 beta, I didn't lock the version which may have caused some problems because of changes in the new React Router 4 Beta API. This boilerplate has a lot of "bleeding edge" stuff, so sadly sometimes things will break due to API changes, but I'll do my best to keep fixing things once that happens.
Did the update work for you @hillscottc ?
I am getting the Invariant Violation in
I think the problem is in the dependencies that are specified imprecisely or really bleeding-edge. Specifically, these:
Yarn complains that:
webpack and webpack-dev-server have a solid 2.2.0 release. Specifying it as just
beta
could be problematic. And react:router:next seems shaky too.Trying to tweak these, then
rm -rf node_modules && yarn
, seems to have given me the broken build. The deps, as they are, seem a little brittle. I'm playing with it to see if I can make a more definitive suggestion.