just out of curiosity, why the cache bust flag? all of the apps i've worked on it was advantageous to assume that anything loaded through require.js *could* be cached (simplifies deployments, provides easy optimizations, etc.). it seems like you'd add the cache bust flag here if your module required the results of an api call, which is common enough, but then it sacrifices that invariant that you can cache anything that's require'd.