<story><title>React Server</title><url>https://react-server.io/</url></story><parent_chain><item><author>pault</author><text>This is exactly what I&amp;#x27;m talking about though, how many different libraries are there for routing alone? How can anyone make a reasonably informed choice between them? It&amp;#x27;s madness!</text></item><item><author>ucarion</author><text>If you&amp;#x27;re gonna use React Router and Redux, you should also check out react-router-redux:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;reactjs&amp;#x2F;react-router-redux&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;reactjs&amp;#x2F;react-router-redux&lt;/a&gt;</text></item><item><author>buchanaf</author><text>I&amp;#x27;ve always used React Router for routing. It&amp;#x27;s super flexible and plays very nicely with Redux and server-side rendering. In terms of syncing up state to views, you might want to look into &amp;#x27;redial&amp;#x27; and &amp;#x27;react-redux&amp;#x27;, which are just higher-order components that ensure your React components can injected with the necessary state.</text></item><item><author>pault</author><text>This is interesting, especially since I just spent the last two weeks setting up a boilerplate for a universal react&amp;#x2F;redux SPA on spec for a new client. I enjoy the flexibility but the need to develop a deep working knowledge of several independent libraries, transpilers, and build tool configuration files (each of which has several competing options with their own way of doing things) just to get to hello world is cost-prohibitive for most people, I&amp;#x27;m sure. At the same time, I&amp;#x27;m hesitant to go &amp;quot;all in&amp;quot; on a stack that I haven&amp;#x27;t heavily researched myself. If the developers are reading, can you go into some details about how you handle routing and data stores? Are you using off the shelf libraries or have you rolled your own?</text></item></parent_chain><comment><author>crucialfelix</author><text>I want a website that rates packages in npm with more possibly useful heuristics:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  num dependencies (shallow, deep)
  total size of node_modules
  installed size (correct use of npmignore etc)
  code quality (McCabe, jslint, jshint)
  typescript&amp;#x2F;flow&amp;#x2F; jsdoc string types etc
  test coverage
  frequency of releases
  documentation coverage
  documentation text analysis: pretentiousness, overly laconic, bro speak
  has a F-ing README so we could at least have some idea what the hell it is
  number of blog and link references
  number of authors
  reputation of authors based on their other packages
  open&amp;#x2F;closed issues&lt;/code&gt;&lt;/pre&gt;
Make the stats available so others can build indices and ranking algorithms based on these.</text></comment>
<story><title>React Server</title><url>https://react-server.io/</url></story><parent_chain><item><author>pault</author><text>This is exactly what I&amp;#x27;m talking about though, how many different libraries are there for routing alone? How can anyone make a reasonably informed choice between them? It&amp;#x27;s madness!</text></item><item><author>ucarion</author><text>If you&amp;#x27;re gonna use React Router and Redux, you should also check out react-router-redux:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;reactjs&amp;#x2F;react-router-redux&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;reactjs&amp;#x2F;react-router-redux&lt;/a&gt;</text></item><item><author>buchanaf</author><text>I&amp;#x27;ve always used React Router for routing. It&amp;#x27;s super flexible and plays very nicely with Redux and server-side rendering. In terms of syncing up state to views, you might want to look into &amp;#x27;redial&amp;#x27; and &amp;#x27;react-redux&amp;#x27;, which are just higher-order components that ensure your React components can injected with the necessary state.</text></item><item><author>pault</author><text>This is interesting, especially since I just spent the last two weeks setting up a boilerplate for a universal react&amp;#x2F;redux SPA on spec for a new client. I enjoy the flexibility but the need to develop a deep working knowledge of several independent libraries, transpilers, and build tool configuration files (each of which has several competing options with their own way of doing things) just to get to hello world is cost-prohibitive for most people, I&amp;#x27;m sure. At the same time, I&amp;#x27;m hesitant to go &amp;quot;all in&amp;quot; on a stack that I haven&amp;#x27;t heavily researched myself. If the developers are reading, can you go into some details about how you handle routing and data stores? Are you using off the shelf libraries or have you rolled your own?</text></item></parent_chain><comment><author>civilian</author><text>My heuristic is:&lt;p&gt;1. Google for a blog comparing them, and eliminate any candidates with major red flags&lt;p&gt;2. Go with the one that has the most stars on it&amp;#x27;s github repo.</text></comment>