aocvr

This blog post does raise the question of what’s going to happen to Stream Framework, now that the hosted version is diverging so clearly...

> You'll also lose a lot of control over your queries which was a big reason for me to move from Django/Rails/etc. style tools to trying out GraphQL.

For restricting queries, an option is using persisted queries (e.g. https://dev-blog.apollodata.com/persisted-graphql-queries-wi...).

The idea is nice, having full control in development while locking down allowed queries in production.

You'd still have to deal with the problems you mentioned in development, some of which are indeed a little ugly (at least currently).

This thread may be interesting to you: https://news.ycombinator.com/item?id=11567135 (Stripe - BYOT: Bring your own team)

create-react-app offers an 'eject' option, which makes all the configuration visible and adjustable. Ejecting can be used as a starting point from which you can further modify and customize a project.

Upgrading from 3 to 4 is not required. Version 3 is still maintained. It's not ideal since there will probably be no future major 3 versions, but no one is forced to make a 'big breaking change' strictly speaking.

> We intend to keep supporting the 3.x branch indefinitely (published separately on npm to aid in migration), although there will likely not be any future major versions based on that code. 4.0 is the future, but we won't leave you hanging if you want to stick with 2.x/3.x.

https://github.com/ReactTraining/react-router/releases/tag/v...

Previously discussed here: https://news.ycombinator.com/item?id=12511419

http://www.reactnativeexpress.com is a great resource.

The projects listed here under "Web" try to achieve that: http://overconstrained.io/