-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support server-rendered React #328
Comments
额,单元测试,不然没法跑
Eward Song <notifications@github.com>于2017年2月11日 周六20:28写道:
… 这个还用 babel-registry 了,
https://github.com/eggjs/egg-view-react/blob/master/test/fixtures/apps/view-react-test/app/controller/test.js
,这样不好吧
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#328 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAWA1ReloGtYdoXKr4QokxhMfss4XiIrks5rbaligaJpZM4L5eeQ>
.
|
建议出 |
egg-next看到有人写了一个 |
强烈建议使用 前端构建都是一个复杂的过程。而 如果单独写一个 |
之前 next.js 1.x 的时候,好像对 koa 的支持不好,要 hack 的方式,现在不知道怎么样了。 可以单独写个 |
我前一阵子研究 next.js 的时候还是不支持 koa 的,现在 koa 接入 next 都是通过设置 |
基于Egg + React + Webpack3/Webpack2 多页面和单页面服务端渲染同构工程骨架项目: https://github.com/hubcarl/egg-react-webpack-boilerplate |
Hi, I am working on https://github.com/djyde/serlina and its Egg binding https://github.com/serlina-community/egg-serlina I think this is the best serverside-rendering solution for Egg application! https://medium.com/@djyde/serlina-a-progressive-react-serverside-rendering-framework-a4de2d71d984 |
@djyde cool~ could add it to https://github.com/eggjs/awesome-egg |
@djyde serlina look beautiful! |
Hi, I've been working on a EggJS plugin that integrates NextJS. egg-frost I have been able to set this plugin and render pages using NextJS render engine (in development mode). I hope it helps. Feedback is always welcome 😄 |
Read the document but don't use |
@dead-horse 给个导致很多中间件失败的demo ,如果导致了你怎么处理的? |
like https://github.com/zeit/next.js/
The text was updated successfully, but these errors were encountered: