dan
Is there anything we need to do on our side for this? I don't understand from reading this issue.
Can you explain your use case in more detail? While you asked this earlier, I wonder if I misunderstood your use case.
Thanks for sharing the use cases. We might support this eventually but for now I recommend either separate apps or ejecting and manually configuring Webpack.
I agree it's something we'd like to see in the future.
@GioLogist My opinion is this is incredibly convoluted. You are trying to use a simple tool (CRA) for a more complex use case (multiple entry points). It's just **not supported**....
@bradfordlemley Thanks a lot for jumping on that issue btw. I'm sorry repo infra changes are being a bit disruptive right now; hopefully we can review them soon!
We also merged Jest 22 into `next` branch so you might want to use that as a base.
FWIW it's probably not going to be important soon because with React 16 we plan to have separate precompiled bundles for development and production, and just one switch.
We don't have Fiber-compatible implementation of SSR but the plan is to figure it out for 16 release. By that time, we intend to have `react-dom-server.node-dev.js` and `react-dom-server.node-prod.min.js` loaded depending...
(I should say that, of course, refreshing helps. The mess up only occurs when `label.jsx` is reevaluated after a newly added file is imported.)