I've had the opposite experience to you. It took a little while to understand what was going on but once I did, I set up a project template that I've been able

I've had the opposite experience to you. It took a little while to understand what was going on but once I did, I set up a project template that I've been able to use in all projects with little in the way of changes. Dev with asynchronous loading and production with built file. The best thing about it is I use jade for my template language and it can be configured to precompile the jade in the bill step, allowing me to use jade in the browser on older browsers. Also as mentioned in a sibling comment I use the same config file for building and development. This isn't specific to requirejs but it was also possible to work it into the asset pipeline of my backend system so that in production it compiles, caches and serves the built file and in dev it uses the asynchronous loader. The only issue I've run into is the same as the flotr2 issue described in the post, which it sounds like there is an easy fix for ski look forward to trying it out.