hot reloading sometimes fails because server doesn't provide CORS header #45
Description
I've seen this at least once, though I haven't thoroughly investigated why it doesn't always fail...
I think the eventual solution may be to:
- use
webpack-dev-middleware - add an index route that:
- requests the meteor page from
localhost:3000 - injects the bundles into the HTML (I also want to make it inject a React commons bundle in the right place so that the fork of
react-packagescan use it) - serves it up
- requests the meteor page from
That approach may interfere with automatic app caching via whatever that Meteor package for app caching is, I don't know. It would be so much better if you could get Meteor to put handwritten <script> tags in a specific order in the <head> though...