[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8},"actionData","errors","root",{"_11":-5},"routes/user.$name.topics",{"_9":10,"_11":12,"_13":14,"_15":16,"_17":18,"_19":16},"topics",[33],"user",{"_20":21,"_13":14,"_22":23,"_24":14,"_25":26,"_27":18,"_28":16,"_29":30,"_31":32},"loginname","kimjuny","page",1,"limit",20,"total","id","30023","avatar_url","https://avatars1.githubusercontent.com/u/9837872?v=4","githubUsername","create_at","2017-09-08 05:01:43.92","score","topic_count","reply_count",3,"is_star",false,{"_20":34,"_35":21,"_36":37,"_38":39,"_40":41,"_42":43,"_44":32,"_45":32,"_29":46,"_47":48,"_25":49,"_50":51},"27634","author_id","tab","share","content","如果你还不是很了解什么是同构，不妨请先自行Google。\r\n\r\n现在市面上有不少优秀的同构示例模板：\r\n\r\n* 其中仅有一部分能覆盖所有常见同构难题\r\n* 配置比较复杂，很多黑科技，不易上手、不易扩展\r\n* 几乎都使用express、使用koa作为后端环境的简直是千里挑一 TAT\r\n\r\n### 该模板解决了如下常见难题:\r\n\r\n* (重点)开发环境的代码热更新问题 - Browser端的热替换(不刷新页面)、Server端的热更新(无需重启node服务器)\r\n* 开发环境和生产环境尽量保持环境一致 - 避免环境不一致导致的奇怪bug\r\n* (重点) 开发和生产环境的代码分割 - 按需加载、按路由加载脚本(javascript)和样式(css)\r\n* 尽量使用最新的官方组件 - 如react-router-v4，现在市面上很多样板还都只能用v3实现\r\n* 尽量使用官方提倡的架构 - 如使用reac-router提倡的route config方式、\broute config中实现数据load\r\n* (重点)完美结合koa和redux-thunk的async/await编程，实现真正的同构\r\n* checksum问题\r\n* (重点)koa作为后端\r\n\r\n### 配置简单到让你发指:\r\n\r\n好吧，既然解决这么多问题，是不是配置过程很恶心？答：不是的。整个项目的核心配置就在以下的2 * 2文件中：\r\n\r\n--- 开始 ---\r\n\r\nconfig/webpack.dev.config.js、src/development.js - 开发环境配置\r\n\r\nconfig/webpack.prod.config.js、src/production.js - 生产环境配置\r\n\r\n--- 结束 ---\r\n\r\n就这样简单... 这样留下足够的空间让使用者加入一些自己喜欢的自定义功能。\b\r\n\r\n好了废话不多说，代码请直戳Github仓库地址：[Koa-React-Universal](https://github.com/kimjuny/koa-react-universal)\r\n\r\nhttps://github.com/kimjuny/koa-react-universal\r\n\r\n代码目前仍处于迭代阶段（有些额外功能还需补充上），但是开发、生产、测试环境已经配置完毕。\r\n\r\n### :slight_smile: 如果觉得好用，请送上star，请尽情fork :slight_smile:\r\n\r\n一个简单地DEMO：搜索github代码仓库（仿github界面）\r\n\r\n![screenshots_00](https://raw.githubusercontent.com/kimjuny/koa-react-universal/master/docs/record.gif)\r\n\r\n各位如果有什么好的建议也欢迎留下issue、PR，或者在下方留言也可以!","title","【分享】React Koa2 同构（服务端渲染）轻量级模板（boilerplate）","last_reply_at","2018-10-10 09:16:57.142","good","top",4,"visit_count",4772,"2017-09-08 05:02:56.393","author",{"_13":14,"_22":23}]